FlightGear wiki - User contributions [en]

Howto:Understand console output

2011-01-02T06:20:23Z

Airbird1: /* Tried to initialize a non-existent engine! */ Added explanation

This document lists '''[[FlightGear]] errors''', how to get rid of them and other '''console output'''. If FlightGear quits but does not give you any error, try increasing the [[FlightGear Launch Control#Debugging|Log Level]].

Errors can appear in various locations, but the most common one is the console (a black window), which pops up when you run fgfs.exe.

==Errors with known solutions==
===Airports/.... ... Done===
This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG_SCENERY]]/Airports</tt> directory.

===Base package check failed ... Found version [none] at: ... Please upgrade to version:===
* FlightGear was unable to find the [[$FG_ROOT]] directory. Set it using the <tt>--fg-root=</tt> commandline option.
* When using [[CVS]] with binaries, the data must match the binary. You cannot use data from a different date than the binary's release date.

===condition: comparison without property[1] or value===
A condition (like <tt><less-than></tt> or <tt><equals></tt>) exists, without either:
* a property to check
* a value to check the property against

===Could not find at least one of the following objects for animation:===
This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. Also in the .xml file make sure that there are not spaces at the beginning or end of the object name. If you are not the aircraft's author you can safely ignore such warnings.

===creating 3D noise texture... DONE===
Tells you that a new noise texture is created. It is not an error and can be ignored.

===Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified====
Try changing the [[FlightGear Launch Control#Page Four - Options and Run|BPP]] value of your FlightGear setup. If that does not work, your graphics card is probably not able to run FlightGear 1.9 and higher. Another graphics card, or an older FlightGear version will likely "fix" the problem.

===Error: bind() failed in make_server_socket()===
When using [[Howto: Multiplayer|multiplayer]] or socket input, this usually means you specified an invalid ip address or the port is in use. Note: for multiplayer, you don't need to use the ''--multiplay=in,...'' option at all, FlightGear (since version 1.0) figures out the proper setting automatically. Only use when you know what you are doing.

===Error Building Technique: findAttr: could not find attribute bool===
Make sure that your data and source (or binary) match. They must be from the same date, to provide the best performance.

===Error: connect() failed in make_client_socket() SG_IO_OUT socket creation failed===
Your computer is not connected with the internet.

===Error: RenderTexture requires the following unsupported OpenGL extensions...===
Your graphics card doesn't support some graphics feature that FG requires. Update your drivers, change the BPP value and/or try disabling some of the visual goodies like [[3D Clouds]].

===Failed to find .... in apt.dat.gz===
You need to edit ATC/default.tower and ATC/default.atis. You can open these files with any text editor. Either remove or fix the entries containing your airports ICAO code (like KSFO).

===Failed to locate aircraft carrier = ...===
FlightGear is unable to find a [[Aircraft carrier|carrier]] under the set name. Check your commandline (<tt>--carrier=...</tt>) or the [[FlightGear Launch Control#Page Three - Airport Selection|airport page]] of the launcher.

'''Hint:''' Make sure your park position and carrier name is correct. See the [[Howto: Carrier|wiki's carrier page]] for details.

===Failed to open file ...===
Check if the file exists on your system. If the missing file is a scenery object; be sure you have the latest [http://scenemodels.flightgear.org/download/SharedModels.tgz Shared Models] from the [[FlightGear Scenery Database]].

===Fatal error: mismatched tag ...===
In some .xml file, an opening tag (like <tt><sim></tt>) does not match its closing tag (like <tt></sim></tt>). This error is hard to track down, best method is to comment (place code between <nowiki></nowiki>) most of the aircraft. Then uncomment code one by one, until the error appears again.

'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a tag is mis-matched and which tag is mis-matched. You'll probably know there's a problem if IE displays an error message.

===Fatal error: name must begin with alpha or '_'===
This error comes up when a property should be formed of which the name does not start with a letter of the alphabet or _. If this error only happens with certain planes, contact their authors.

===Fatal error: unclosed token===
A token (<nowiki></nowiki>) has been started, but not closes. Add <nowiki>--></nowiki> at the correct line.

'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a comment/token is not closed.

===FGMultiplayMgr::MP_ProcessData: No such file or directory===
This is telling you that there's someone online on the multiplayerserver, using a plane that you do not have installed on your own system. In order to remove the error (and see the other plane) you have to install the plane that the other pilot is using.

===FGMultiplayMgr - No receiver port, Multiplayermode disabled===
FlightGear [[Howto: Multiplayer|multiplayer]] has not been set.

===FGPropertyManager::GetNode() No node found for ... In component: ... unknown property ... referenced. Aborting===
FlightGear found a reference in the [[FDM]] to a non-existing property.

===FGPropertyManager::GetNode() No node found for ... The property ... is undefined.===
FlightGear found a reference in the [[FDM]] to a non-existing property. Keep in mind that JSBSim reads the FDM from top to bottom. Properties should always be created before they are needed somewhere.

===Fgtzfile_read(): : Invalid argument Fatal error: Timezone reading failed===
This one is caused by wrong line ending in a timezone file. Solution might be to download the Timezone/time.tab file manually from [http://gitorious.org/fg/fgdata/blobs/raw/master/Timezone/zone.tab Gitorious] (Right mouseclick > Save target as) and overwrite the file in <tt>[[$FG_ROOT]]/Timezone/time.tab</tt> with it.

===Found unexpected subsystem: system exiting. JSBSim failed to load aircraft and/or engine model===
You are probably trying to run an aircraft on a out-of-date version of FlightGear. The planes on the official download page are intended to be used with the latest version of FlightGear. Usage on any older systems may not work.

===freeglut (fgfs): Unable to create direct context rendering for window 'FlightGear' This may hurt performance===
This reports that you do not have proper hardware accelerated 3D (direct rendering) configured.

===Gate ... doesn't seem to have routes associated with it===
A startup location in the [[Interactive Traffic#Ground networks|groundnetwork]] is not (properly) connected to a taxi route. Contact the airport author, or import the network to [[TaxiDraw]] and run the Verify network command to find the corrupted gate.

===glLinkProgram "" Failed===
Update your drivers; they have to support atleast OpenGL 2.0 for FlightGear 2.0 and later.

===loading scenario '...'===
This is not an error. It shows that an [[AI Systems#AI Models|AI scenario]] is loaded.

===Model not found: ...===
This one tells you that FlightGear was unable to find a certain file. The nice thing is that it also tells you excactly what file.

# Check if the file really does not exist at your computer.
# Try to locate the file in which the missing file is referenced. This is likely to be <tt>-set.xml</tt> in the root directory of the loaded [[aircraft]]. Between the <model> tags, the base model file is referenced. This file references to all other models that are displayed with the aircraft.
# Contact the aircraft author with a detailed bug-report, in which you state the excact location of the missing file and (if you found it) the file in which it is referenced.

===Nasal runtime error: nil used in numeric context===
This error is [[Nasal]] triggered by a Nasal file (the console should show what file (and line) and from where it was referenced). The Nasal script tried to do something with a [[Property Tree|property]] with an empty value. A solution is to fill the property before the Nasal is loaded. This can be done by setting the property in an [[aircraft]]'s <tt>-set.xml</tt> file or by adding a [[Nasal scripting language#Listeners and Signals|listener]] to the script.

[[Howto: Contact the developers|Contact the developers]] if this error is shown for a <tt>[[$FG_ROOT]]/Nasal/</tt> script.

===Near camera not rendering===
[[Image:Near_camera_off.png|500px]]

If you screen looks like the image above; make sure you have at least [[OSG]] version 2.7.6.

===No render bin name specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===No render bin number specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===... not a valid win32 application===
This Windows error could have various reasons to pop up. Usually, the file that is causing troubles is mentioned. Re-installing this file might solve the problem.

===OBJECT_SIGN: unsupported glyph `.'===
Check the OBJECT_SIGN lines in the .stg file of the tile that was loaded when this error showed up.

===OpenAL error <AL_INVALID_VALUE>: bind source <alGenSources> Failed to generate audio source.===
This error is probably displayed because of some misdirected audio settings in the [[aircraft]]s setup. Check the -sound.xml file of the aircraft and see if all files refered to really exist. If not, try to contact the author of the plane, so he can fix the problem in the [[FlightGear CVS|CVS]] version or solve the problem yourself and let someone commit the patch.

===OpenAL error (AL_INVALID_VALUE): constructor (alBufferData) Fatal error: Failed to buffer data.===
Disabling sound is a temporarily solution for this problem.

===osgDB ac3d reader: could not find texture...===
See [[#Failed to open file ...|Failed to open file ...]]

===osgDB ac3d reader: detected surface with less than 3 vertices!===
In one of the loaded models a non-existing surface is found. This can be a single line (sometimes used to simulate thin wires) or a fault in the model.

===Program's vertex attrib binding ..., usrAttr...===
Tells you that an effect binded certain attributes to a [[Shaders|shader]].

===QNAN===
(Q)NAN stands for (Quiet) Not A Number, produced by 0/0 or other floating point break downs. There can be various causes for this:
* Using a "flap start" value of 0 in the [[YASim]] [[FDM]]. Use some small value like 0.001 instead.

===Scaling image...===
This means a texture, whether in the scenery on your aircraft or anyone elses (when multiplayer is enabled), is not sized to powers of two. All textures in FlightGear have to be sized to power of two (eg. 16*16, 32*64, 32*1024). As of version 1.9 textures are resized automaticly, but it does slow your computer down, so it's better to resize the noted textures.

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

===The system cannot find the file specified===
If you are running Windows Vista; start by looking in <tt>C:\Users\Owner\AppData\Local\VirtualStore</tt> and seeing if you have a folder called FlightGear in there. If you do, cut-and-paste (merge) that one with <tt>C:\Program Files\Flightgear</tt> and try to launch FlightGear again.

'''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible.

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

===Traffic manager could not find airport===
There is either an airport missing from apt.dat, or there is a wrong ICAO code in a [[Interactive Traffic#Building Traffic Files|traffic file]]. An airport missing from apt.dat could be due to a recent opening.

===Unable to choose requested pixel format===
Error should be solved as of version 1.9. If not, try changing your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] and/or resolution.

===Unable to find airport details for .... in FGTower::Init()===
This error can be surpressed by disabling [[Interactive Traffic|AI Traffic]], via the AI/ATC [[menu]].

The error appears when an airport in <tt>[[$FG_ROOT]]/Airports/apt.dat.gz</tt> cannot be found in <tt>[[$FG_ROOT]]/ATC/default.tower</tt> and <tt>[[$FG_ROOT]]/ATC/default.atis</tt>. Renaming the airports in the apt.dat.gz file ór in both default ATC files will fix the problem.

===Unable to open aircraft directory===
The [[aircraft]] that you are trying to run most likely relies on another aircraft, which you did not install (yet). The error shows what aircraft, so go download that one!
=== Unexpected tag '...' found in YASim aircraft description===
FlightGear found a non-existing tag in the [[FDM]] of the aircraft you are trying to launch. If you have not changed the original aircraft, contact the aircraft author. Else, check the FDM througly for mistakes.

Also, make sure you didn't force a FDM to be loaded.
* '''Commandline:''' <tt>--fdm=...</tt> should be left out.
* '''[[FGRun]]:''' <tt>Advanced > Flight Model</tt> should be set to jsb (which will leave the whole command out of the commandline, so you can use this setting with any FDM).

=== Unknown ... aircraft: ... defaulting to C172 ===
FlightGear is unable to load the forced [[FDM]] (set through <tt>--fdm=...</tt> or via <tt>Advanced > Flight Model</tt> in [[FGRun]]) for this aircraft. FlightGear automatically picks the right FDM for each aircraft, so there is no need to set it manually, unless you know what you are doing. In the Flight Model dialog of FGRun, set the FDM to <tt>jsb</tt>; that is the "auto setting".

===Unknown exception to the main loop. Aborting... Possible cause: No such file or directory===
This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear_Launch_Control#Debugging|log level]] to debug and repeating excactly what you did when the error came up, might provide some more information on what FlightGear was doing when the error occurred.
* Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work.
* Changing the resolution to a smaller one might work as well.

===WARNING: Couldn't convert texture...===
You are trying to run an aircraft not compatible with your FlightGear version. Most of the time, this error appears when you fly an aircraft, textured with .png files on versions older than 1.9. Convert the textures manually to .rgb or upgrade your FlightGear version.

===Warning: Could not find plugin to read objects from file ...===
A library is missing from your computer. Therefore, certain fileformats cannot be read. Try to reinstall/update [[OSG]], as the libraries used by FlightGear should be part of the standard package.

===Warning: Picked up TriangleIntersect===
Reduce your [[FlightGear Launch Control#Debugging|Log Level]] to alert. Or [[Showstoppers|send the fgfs output to /dev/null (unix systems) or 2>nul (Windows)]]. The errors might still be shown, but do not affect the sim anymore.

===Warning: TangentSpaceGenerator: unknown primitive mode 9===
This is an [[OSG]] error, showing up when an effect needs tangent vectors, but polygons are not support. The error itself can be ignored, altough some [[shaders]] may look wrong. Shader developers should try to minimise the use of polygons and use triangles and quads instead.

===YASim SOLUTION FAILURE: Solution failed to converge after 10000 iterations===
Some control in the [[YASim]] [[FDM]] is too weak, according to YASim, to control the aircraft. An effectiveness tag will be required in the FDM to solve this error.

===YASim SOLUTION FAILURE: Zero length fuselage===
There is a problem in the [[FDM]]. A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.

===FGMultiplayerMgr::Open - Failed to bind receive socket===

This means FlightGear was unable to open the listening network socket required by the --multiplay=in option. Frequently this option can be omitted and FlightGear will figure out the necessary parameters automatically.
Common reasons are:
* Address given in the option does not resolve to one of the IP addresses of the local machine. This parameter should only be required if you want to fine-tune the network behavior. Omitting it directs FlightGear to listen on all local interfaces automatically. Example:
--multiplay=in,10,,5001
Notice that you still need the comma.
* The UDP port given in the option (or the default port 5000 if no option given) is already in use. Verify nothing is using the port.

==Errors without known solutions==
Please take a look at the upcoming errors and see if you know a solution to get rid of them. Your additions are greatly appreciated!

===Aircraft propulsion element has problems in file ...===

===AL Error (fx): Invalid Value at pitch and gain===
The sound effect's pitch (high or low) and gain (volume multiplication factor) values are not valid.

===AL Error (sound manager): Invalid Operation at update===

===AL Error (sound manager): Invalid Value at buffer add data No such buffer!===

===Failed to execute command nasal===
Has something to do with the [[Nasal]] scripting language used by FlightGear.

===Failed to tie (or untie while closing) property ... to object methods===
A JSBSim error.

===FGMultiplayMgr::MP_ProcessData - message from ... has invalid length!===

===FGMultiplayMgr::MP_ProcessData: Result too large===

===GPS: malformed route, index=1===

===Mesa 7.3 implementation error: bad texture level in r300UploadSubImage===
http://www.flightgear.org/forums/viewtopic.php?f=2&t=6706&start=0&st=0&sk=t&sd=a

===Nasal runtime error: stack overflow===

===No image file for texture, using white===
A [[Shaders|shader]] error, possibly you (or the developer) have/has not specified a texture for a surface while modeling the aircraft model in AC3D, Blender, Wings...

===No path in /sim/sound/path===
You (or the developer) have/has not specified a proper sound file in the aircraft's -set.xml file.

===OBJECT_SIGN: unexpected } in sign contents===

===OpenAL error (AL_ILLEGAL_COMMAND): set_source_pos===

Has something to do with OpenAL not understanding where the sound comes from.

===OpenAL error (AL_ILLEGAL_COMMAND): set_volume===

Has something to do with OpenAL not understanding the sound volume.

===PT_vs_hpt: ran out of layers===
This is issued from the atmosphere implementation in FlightGear's environment system. A comment in the code says: "''should never get here''". Please provide input when this happens: excessive altitudes? Negative altitudes?

===Tried to initialize a non-existent engine!===
The developer of the aircraft did not code the engine properly.

'''Developers:''' Check that the engine.xml file, FDM.xml, and -set.xml is coded properly.

===Unknown Chunk: ***UNKNOWN*** (0xA08A)===

===Warning: detected OpenGL error 'invalid value' after RenderBin::draw(,)===
This warning is generated from OSG. Set your environment variable
OSG_NOTIFY_LEVEL=FATAL

===Warning: GraphicsWindowWin32::grabFocus() - Failed grabbing the focus===
It seems that this happens when you have another window open and you are "focusing" (the window is active) on it. FlightGear will try to grab itself infront of the other window.

===WARNING: PUI: Too many live puInterfaces open at once!===
Appears when printing large outputs (very) frequently on the screen.

===Warning: State::drawQuads(0, 154400) too large handle in remapping to ushort glDrawElements===

[[Category:Howto|Console output]]

[[fr:Howto: Débarrassez-vous des erreurs les plus fréquentes]]

Howto:Understand console output

2011-01-02T06:14:08Z

Airbird1: /* Failed to execute command nasal */ Added ***possible*** explanation

This document lists '''[[FlightGear]] errors''', how to get rid of them and other '''console output'''. If FlightGear quits but does not give you any error, try increasing the [[FlightGear Launch Control#Debugging|Log Level]].

Errors can appear in various locations, but the most common one is the console (a black window), which pops up when you run fgfs.exe.

==Errors with known solutions==
===Airports/.... ... Done===
This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG_SCENERY]]/Airports</tt> directory.

===Base package check failed ... Found version [none] at: ... Please upgrade to version:===
* FlightGear was unable to find the [[$FG_ROOT]] directory. Set it using the <tt>--fg-root=</tt> commandline option.
* When using [[CVS]] with binaries, the data must match the binary. You cannot use data from a different date than the binary's release date.

===condition: comparison without property[1] or value===
A condition (like <tt><less-than></tt> or <tt><equals></tt>) exists, without either:
* a property to check
* a value to check the property against

===Could not find at least one of the following objects for animation:===
This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. Also in the .xml file make sure that there are not spaces at the beginning or end of the object name. If you are not the aircraft's author you can safely ignore such warnings.

===creating 3D noise texture... DONE===
Tells you that a new noise texture is created. It is not an error and can be ignored.

===Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified====
Try changing the [[FlightGear Launch Control#Page Four - Options and Run|BPP]] value of your FlightGear setup. If that does not work, your graphics card is probably not able to run FlightGear 1.9 and higher. Another graphics card, or an older FlightGear version will likely "fix" the problem.

===Error: bind() failed in make_server_socket()===
When using [[Howto: Multiplayer|multiplayer]] or socket input, this usually means you specified an invalid ip address or the port is in use. Note: for multiplayer, you don't need to use the ''--multiplay=in,...'' option at all, FlightGear (since version 1.0) figures out the proper setting automatically. Only use when you know what you are doing.

===Error Building Technique: findAttr: could not find attribute bool===
Make sure that your data and source (or binary) match. They must be from the same date, to provide the best performance.

===Error: connect() failed in make_client_socket() SG_IO_OUT socket creation failed===
Your computer is not connected with the internet.

===Error: RenderTexture requires the following unsupported OpenGL extensions...===
Your graphics card doesn't support some graphics feature that FG requires. Update your drivers, change the BPP value and/or try disabling some of the visual goodies like [[3D Clouds]].

===Failed to find .... in apt.dat.gz===
You need to edit ATC/default.tower and ATC/default.atis. You can open these files with any text editor. Either remove or fix the entries containing your airports ICAO code (like KSFO).

===Failed to locate aircraft carrier = ...===
FlightGear is unable to find a [[Aircraft carrier|carrier]] under the set name. Check your commandline (<tt>--carrier=...</tt>) or the [[FlightGear Launch Control#Page Three - Airport Selection|airport page]] of the launcher.

'''Hint:''' Make sure your park position and carrier name is correct. See the [[Howto: Carrier|wiki's carrier page]] for details.

===Failed to open file ...===
Check if the file exists on your system. If the missing file is a scenery object; be sure you have the latest [http://scenemodels.flightgear.org/download/SharedModels.tgz Shared Models] from the [[FlightGear Scenery Database]].

===Fatal error: mismatched tag ...===
In some .xml file, an opening tag (like <tt><sim></tt>) does not match its closing tag (like <tt></sim></tt>). This error is hard to track down, best method is to comment (place code between <nowiki></nowiki>) most of the aircraft. Then uncomment code one by one, until the error appears again.

'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a tag is mis-matched and which tag is mis-matched. You'll probably know there's a problem if IE displays an error message.

===Fatal error: name must begin with alpha or '_'===
This error comes up when a property should be formed of which the name does not start with a letter of the alphabet or _. If this error only happens with certain planes, contact their authors.

===Fatal error: unclosed token===
A token (<nowiki></nowiki>) has been started, but not closes. Add <nowiki>--></nowiki> at the correct line.

'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a comment/token is not closed.

===FGMultiplayMgr::MP_ProcessData: No such file or directory===
This is telling you that there's someone online on the multiplayerserver, using a plane that you do not have installed on your own system. In order to remove the error (and see the other plane) you have to install the plane that the other pilot is using.

===FGMultiplayMgr - No receiver port, Multiplayermode disabled===
FlightGear [[Howto: Multiplayer|multiplayer]] has not been set.

===FGPropertyManager::GetNode() No node found for ... In component: ... unknown property ... referenced. Aborting===
FlightGear found a reference in the [[FDM]] to a non-existing property.

===FGPropertyManager::GetNode() No node found for ... The property ... is undefined.===
FlightGear found a reference in the [[FDM]] to a non-existing property. Keep in mind that JSBSim reads the FDM from top to bottom. Properties should always be created before they are needed somewhere.

===Fgtzfile_read(): : Invalid argument Fatal error: Timezone reading failed===
This one is caused by wrong line ending in a timezone file. Solution might be to download the Timezone/time.tab file manually from [http://gitorious.org/fg/fgdata/blobs/raw/master/Timezone/zone.tab Gitorious] (Right mouseclick > Save target as) and overwrite the file in <tt>[[$FG_ROOT]]/Timezone/time.tab</tt> with it.

===Found unexpected subsystem: system exiting. JSBSim failed to load aircraft and/or engine model===
You are probably trying to run an aircraft on a out-of-date version of FlightGear. The planes on the official download page are intended to be used with the latest version of FlightGear. Usage on any older systems may not work.

===freeglut (fgfs): Unable to create direct context rendering for window 'FlightGear' This may hurt performance===
This reports that you do not have proper hardware accelerated 3D (direct rendering) configured.

===Gate ... doesn't seem to have routes associated with it===
A startup location in the [[Interactive Traffic#Ground networks|groundnetwork]] is not (properly) connected to a taxi route. Contact the airport author, or import the network to [[TaxiDraw]] and run the Verify network command to find the corrupted gate.

===glLinkProgram "" Failed===
Update your drivers; they have to support atleast OpenGL 2.0 for FlightGear 2.0 and later.

===loading scenario '...'===
This is not an error. It shows that an [[AI Systems#AI Models|AI scenario]] is loaded.

===Model not found: ...===
This one tells you that FlightGear was unable to find a certain file. The nice thing is that it also tells you excactly what file.

# Check if the file really does not exist at your computer.
# Try to locate the file in which the missing file is referenced. This is likely to be <tt>-set.xml</tt> in the root directory of the loaded [[aircraft]]. Between the <model> tags, the base model file is referenced. This file references to all other models that are displayed with the aircraft.
# Contact the aircraft author with a detailed bug-report, in which you state the excact location of the missing file and (if you found it) the file in which it is referenced.

===Nasal runtime error: nil used in numeric context===
This error is [[Nasal]] triggered by a Nasal file (the console should show what file (and line) and from where it was referenced). The Nasal script tried to do something with a [[Property Tree|property]] with an empty value. A solution is to fill the property before the Nasal is loaded. This can be done by setting the property in an [[aircraft]]'s <tt>-set.xml</tt> file or by adding a [[Nasal scripting language#Listeners and Signals|listener]] to the script.

[[Howto: Contact the developers|Contact the developers]] if this error is shown for a <tt>[[$FG_ROOT]]/Nasal/</tt> script.

===Near camera not rendering===
[[Image:Near_camera_off.png|500px]]

If you screen looks like the image above; make sure you have at least [[OSG]] version 2.7.6.

===No render bin name specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===No render bin number specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===... not a valid win32 application===
This Windows error could have various reasons to pop up. Usually, the file that is causing troubles is mentioned. Re-installing this file might solve the problem.

===OBJECT_SIGN: unsupported glyph `.'===
Check the OBJECT_SIGN lines in the .stg file of the tile that was loaded when this error showed up.

===OpenAL error <AL_INVALID_VALUE>: bind source <alGenSources> Failed to generate audio source.===
This error is probably displayed because of some misdirected audio settings in the [[aircraft]]s setup. Check the -sound.xml file of the aircraft and see if all files refered to really exist. If not, try to contact the author of the plane, so he can fix the problem in the [[FlightGear CVS|CVS]] version or solve the problem yourself and let someone commit the patch.

===OpenAL error (AL_INVALID_VALUE): constructor (alBufferData) Fatal error: Failed to buffer data.===
Disabling sound is a temporarily solution for this problem.

===osgDB ac3d reader: could not find texture...===
See [[#Failed to open file ...|Failed to open file ...]]

===osgDB ac3d reader: detected surface with less than 3 vertices!===
In one of the loaded models a non-existing surface is found. This can be a single line (sometimes used to simulate thin wires) or a fault in the model.

===Program's vertex attrib binding ..., usrAttr...===
Tells you that an effect binded certain attributes to a [[Shaders|shader]].

===QNAN===
(Q)NAN stands for (Quiet) Not A Number, produced by 0/0 or other floating point break downs. There can be various causes for this:
* Using a "flap start" value of 0 in the [[YASim]] [[FDM]]. Use some small value like 0.001 instead.

===Scaling image...===
This means a texture, whether in the scenery on your aircraft or anyone elses (when multiplayer is enabled), is not sized to powers of two. All textures in FlightGear have to be sized to power of two (eg. 16*16, 32*64, 32*1024). As of version 1.9 textures are resized automaticly, but it does slow your computer down, so it's better to resize the noted textures.

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

===The system cannot find the file specified===
If you are running Windows Vista; start by looking in <tt>C:\Users\Owner\AppData\Local\VirtualStore</tt> and seeing if you have a folder called FlightGear in there. If you do, cut-and-paste (merge) that one with <tt>C:\Program Files\Flightgear</tt> and try to launch FlightGear again.

'''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible.

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

===Traffic manager could not find airport===
There is either an airport missing from apt.dat, or there is a wrong ICAO code in a [[Interactive Traffic#Building Traffic Files|traffic file]]. An airport missing from apt.dat could be due to a recent opening.

===Unable to choose requested pixel format===
Error should be solved as of version 1.9. If not, try changing your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] and/or resolution.

===Unable to find airport details for .... in FGTower::Init()===
This error can be surpressed by disabling [[Interactive Traffic|AI Traffic]], via the AI/ATC [[menu]].

The error appears when an airport in <tt>[[$FG_ROOT]]/Airports/apt.dat.gz</tt> cannot be found in <tt>[[$FG_ROOT]]/ATC/default.tower</tt> and <tt>[[$FG_ROOT]]/ATC/default.atis</tt>. Renaming the airports in the apt.dat.gz file ór in both default ATC files will fix the problem.

===Unable to open aircraft directory===
The [[aircraft]] that you are trying to run most likely relies on another aircraft, which you did not install (yet). The error shows what aircraft, so go download that one!
=== Unexpected tag '...' found in YASim aircraft description===
FlightGear found a non-existing tag in the [[FDM]] of the aircraft you are trying to launch. If you have not changed the original aircraft, contact the aircraft author. Else, check the FDM througly for mistakes.

Also, make sure you didn't force a FDM to be loaded.
* '''Commandline:''' <tt>--fdm=...</tt> should be left out.
* '''[[FGRun]]:''' <tt>Advanced > Flight Model</tt> should be set to jsb (which will leave the whole command out of the commandline, so you can use this setting with any FDM).

=== Unknown ... aircraft: ... defaulting to C172 ===
FlightGear is unable to load the forced [[FDM]] (set through <tt>--fdm=...</tt> or via <tt>Advanced > Flight Model</tt> in [[FGRun]]) for this aircraft. FlightGear automatically picks the right FDM for each aircraft, so there is no need to set it manually, unless you know what you are doing. In the Flight Model dialog of FGRun, set the FDM to <tt>jsb</tt>; that is the "auto setting".

===Unknown exception to the main loop. Aborting... Possible cause: No such file or directory===
This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear_Launch_Control#Debugging|log level]] to debug and repeating excactly what you did when the error came up, might provide some more information on what FlightGear was doing when the error occurred.
* Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work.
* Changing the resolution to a smaller one might work as well.

===WARNING: Couldn't convert texture...===
You are trying to run an aircraft not compatible with your FlightGear version. Most of the time, this error appears when you fly an aircraft, textured with .png files on versions older than 1.9. Convert the textures manually to .rgb or upgrade your FlightGear version.

===Warning: Could not find plugin to read objects from file ...===
A library is missing from your computer. Therefore, certain fileformats cannot be read. Try to reinstall/update [[OSG]], as the libraries used by FlightGear should be part of the standard package.

===Warning: Picked up TriangleIntersect===
Reduce your [[FlightGear Launch Control#Debugging|Log Level]] to alert. Or [[Showstoppers|send the fgfs output to /dev/null (unix systems) or 2>nul (Windows)]]. The errors might still be shown, but do not affect the sim anymore.

===Warning: TangentSpaceGenerator: unknown primitive mode 9===
This is an [[OSG]] error, showing up when an effect needs tangent vectors, but polygons are not support. The error itself can be ignored, altough some [[shaders]] may look wrong. Shader developers should try to minimise the use of polygons and use triangles and quads instead.

===YASim SOLUTION FAILURE: Solution failed to converge after 10000 iterations===
Some control in the [[YASim]] [[FDM]] is too weak, according to YASim, to control the aircraft. An effectiveness tag will be required in the FDM to solve this error.

===YASim SOLUTION FAILURE: Zero length fuselage===
There is a problem in the [[FDM]]. A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.

===FGMultiplayerMgr::Open - Failed to bind receive socket===

This means FlightGear was unable to open the listening network socket required by the --multiplay=in option. Frequently this option can be omitted and FlightGear will figure out the necessary parameters automatically.
Common reasons are:
* Address given in the option does not resolve to one of the IP addresses of the local machine. This parameter should only be required if you want to fine-tune the network behavior. Omitting it directs FlightGear to listen on all local interfaces automatically. Example:
--multiplay=in,10,,5001
Notice that you still need the comma.
* The UDP port given in the option (or the default port 5000 if no option given) is already in use. Verify nothing is using the port.

==Errors without known solutions==
Please take a look at the upcoming errors and see if you know a solution to get rid of them. Your additions are greatly appreciated!

===Aircraft propulsion element has problems in file ...===

===AL Error (fx): Invalid Value at pitch and gain===
The sound effect's pitch (high or low) and gain (volume multiplication factor) values are not valid.

===AL Error (sound manager): Invalid Operation at update===

===AL Error (sound manager): Invalid Value at buffer add data No such buffer!===

===Failed to execute command nasal===
Has something to do with the [[Nasal]] scripting language used by FlightGear.

===Failed to tie (or untie while closing) property ... to object methods===
A JSBSim error.

===FGMultiplayMgr::MP_ProcessData - message from ... has invalid length!===

===FGMultiplayMgr::MP_ProcessData: Result too large===

===GPS: malformed route, index=1===

===Mesa 7.3 implementation error: bad texture level in r300UploadSubImage===
http://www.flightgear.org/forums/viewtopic.php?f=2&t=6706&start=0&st=0&sk=t&sd=a

===Nasal runtime error: stack overflow===

===No image file for texture, using white===
A [[Shaders|shader]] error, possibly you (or the developer) have/has not specified a texture for a surface while modeling the aircraft model in AC3D, Blender, Wings...

===No path in /sim/sound/path===
You (or the developer) have/has not specified a proper sound file in the aircraft's -set.xml file.

===OBJECT_SIGN: unexpected } in sign contents===

===OpenAL error (AL_ILLEGAL_COMMAND): set_source_pos===

Has something to do with OpenAL not understanding where the sound comes from.

===OpenAL error (AL_ILLEGAL_COMMAND): set_volume===

Has something to do with OpenAL not understanding the sound volume.

===PT_vs_hpt: ran out of layers===
This is issued from the atmosphere implementation in FlightGear's environment system. A comment in the code says: "''should never get here''". Please provide input when this happens: excessive altitudes? Negative altitudes?

===Tried to initialize a non-existent engine!===

===Unknown Chunk: ***UNKNOWN*** (0xA08A)===

===Warning: detected OpenGL error 'invalid value' after RenderBin::draw(,)===
This warning is generated from OSG. Set your environment variable
OSG_NOTIFY_LEVEL=FATAL

===Warning: GraphicsWindowWin32::grabFocus() - Failed grabbing the focus===
It seems that this happens when you have another window open and you are "focusing" (the window is active) on it. FlightGear will try to grab itself infront of the other window.

===WARNING: PUI: Too many live puInterfaces open at once!===
Appears when printing large outputs (very) frequently on the screen.

===Warning: State::drawQuads(0, 154400) too large handle in remapping to ushort glDrawElements===

[[Category:Howto|Console output]]

[[fr:Howto: Débarrassez-vous des erreurs les plus fréquentes]]

Howto:Understand console output

2011-01-02T06:10:59Z

Airbird1: /* AL Error (fx): Invalid Value at pitch and gain */ Added ***possible*** explanation

This document lists '''[[FlightGear]] errors''', how to get rid of them and other '''console output'''. If FlightGear quits but does not give you any error, try increasing the [[FlightGear Launch Control#Debugging|Log Level]].

Errors can appear in various locations, but the most common one is the console (a black window), which pops up when you run fgfs.exe.

==Errors with known solutions==
===Airports/.... ... Done===
This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG_SCENERY]]/Airports</tt> directory.

===Base package check failed ... Found version [none] at: ... Please upgrade to version:===
* FlightGear was unable to find the [[$FG_ROOT]] directory. Set it using the <tt>--fg-root=</tt> commandline option.
* When using [[CVS]] with binaries, the data must match the binary. You cannot use data from a different date than the binary's release date.

===condition: comparison without property[1] or value===
A condition (like <tt><less-than></tt> or <tt><equals></tt>) exists, without either:
* a property to check
* a value to check the property against

===Could not find at least one of the following objects for animation:===
This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. Also in the .xml file make sure that there are not spaces at the beginning or end of the object name. If you are not the aircraft's author you can safely ignore such warnings.

===creating 3D noise texture... DONE===
Tells you that a new noise texture is created. It is not an error and can be ignored.

===Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified====
Try changing the [[FlightGear Launch Control#Page Four - Options and Run|BPP]] value of your FlightGear setup. If that does not work, your graphics card is probably not able to run FlightGear 1.9 and higher. Another graphics card, or an older FlightGear version will likely "fix" the problem.

===Error: bind() failed in make_server_socket()===
When using [[Howto: Multiplayer|multiplayer]] or socket input, this usually means you specified an invalid ip address or the port is in use. Note: for multiplayer, you don't need to use the ''--multiplay=in,...'' option at all, FlightGear (since version 1.0) figures out the proper setting automatically. Only use when you know what you are doing.

===Error Building Technique: findAttr: could not find attribute bool===
Make sure that your data and source (or binary) match. They must be from the same date, to provide the best performance.

===Error: connect() failed in make_client_socket() SG_IO_OUT socket creation failed===
Your computer is not connected with the internet.

===Error: RenderTexture requires the following unsupported OpenGL extensions...===
Your graphics card doesn't support some graphics feature that FG requires. Update your drivers, change the BPP value and/or try disabling some of the visual goodies like [[3D Clouds]].

===Failed to find .... in apt.dat.gz===
You need to edit ATC/default.tower and ATC/default.atis. You can open these files with any text editor. Either remove or fix the entries containing your airports ICAO code (like KSFO).

===Failed to locate aircraft carrier = ...===
FlightGear is unable to find a [[Aircraft carrier|carrier]] under the set name. Check your commandline (<tt>--carrier=...</tt>) or the [[FlightGear Launch Control#Page Three - Airport Selection|airport page]] of the launcher.

'''Hint:''' Make sure your park position and carrier name is correct. See the [[Howto: Carrier|wiki's carrier page]] for details.

===Failed to open file ...===
Check if the file exists on your system. If the missing file is a scenery object; be sure you have the latest [http://scenemodels.flightgear.org/download/SharedModels.tgz Shared Models] from the [[FlightGear Scenery Database]].

===Fatal error: mismatched tag ...===
In some .xml file, an opening tag (like <tt><sim></tt>) does not match its closing tag (like <tt></sim></tt>). This error is hard to track down, best method is to comment (place code between <nowiki></nowiki>) most of the aircraft. Then uncomment code one by one, until the error appears again.

'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a tag is mis-matched and which tag is mis-matched. You'll probably know there's a problem if IE displays an error message.

===Fatal error: name must begin with alpha or '_'===
This error comes up when a property should be formed of which the name does not start with a letter of the alphabet or _. If this error only happens with certain planes, contact their authors.

===Fatal error: unclosed token===
A token (<nowiki></nowiki>) has been started, but not closes. Add <nowiki>--></nowiki> at the correct line.

'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a comment/token is not closed.

===FGMultiplayMgr::MP_ProcessData: No such file or directory===
This is telling you that there's someone online on the multiplayerserver, using a plane that you do not have installed on your own system. In order to remove the error (and see the other plane) you have to install the plane that the other pilot is using.

===FGMultiplayMgr - No receiver port, Multiplayermode disabled===
FlightGear [[Howto: Multiplayer|multiplayer]] has not been set.

===FGPropertyManager::GetNode() No node found for ... In component: ... unknown property ... referenced. Aborting===
FlightGear found a reference in the [[FDM]] to a non-existing property.

===FGPropertyManager::GetNode() No node found for ... The property ... is undefined.===
FlightGear found a reference in the [[FDM]] to a non-existing property. Keep in mind that JSBSim reads the FDM from top to bottom. Properties should always be created before they are needed somewhere.

===Fgtzfile_read(): : Invalid argument Fatal error: Timezone reading failed===
This one is caused by wrong line ending in a timezone file. Solution might be to download the Timezone/time.tab file manually from [http://gitorious.org/fg/fgdata/blobs/raw/master/Timezone/zone.tab Gitorious] (Right mouseclick > Save target as) and overwrite the file in <tt>[[$FG_ROOT]]/Timezone/time.tab</tt> with it.

===Found unexpected subsystem: system exiting. JSBSim failed to load aircraft and/or engine model===
You are probably trying to run an aircraft on a out-of-date version of FlightGear. The planes on the official download page are intended to be used with the latest version of FlightGear. Usage on any older systems may not work.

===freeglut (fgfs): Unable to create direct context rendering for window 'FlightGear' This may hurt performance===
This reports that you do not have proper hardware accelerated 3D (direct rendering) configured.

===Gate ... doesn't seem to have routes associated with it===
A startup location in the [[Interactive Traffic#Ground networks|groundnetwork]] is not (properly) connected to a taxi route. Contact the airport author, or import the network to [[TaxiDraw]] and run the Verify network command to find the corrupted gate.

===glLinkProgram "" Failed===
Update your drivers; they have to support atleast OpenGL 2.0 for FlightGear 2.0 and later.

===loading scenario '...'===
This is not an error. It shows that an [[AI Systems#AI Models|AI scenario]] is loaded.

===Model not found: ...===
This one tells you that FlightGear was unable to find a certain file. The nice thing is that it also tells you excactly what file.

# Check if the file really does not exist at your computer.
# Try to locate the file in which the missing file is referenced. This is likely to be <tt>-set.xml</tt> in the root directory of the loaded [[aircraft]]. Between the <model> tags, the base model file is referenced. This file references to all other models that are displayed with the aircraft.
# Contact the aircraft author with a detailed bug-report, in which you state the excact location of the missing file and (if you found it) the file in which it is referenced.

===Nasal runtime error: nil used in numeric context===
This error is [[Nasal]] triggered by a Nasal file (the console should show what file (and line) and from where it was referenced). The Nasal script tried to do something with a [[Property Tree|property]] with an empty value. A solution is to fill the property before the Nasal is loaded. This can be done by setting the property in an [[aircraft]]'s <tt>-set.xml</tt> file or by adding a [[Nasal scripting language#Listeners and Signals|listener]] to the script.

[[Howto: Contact the developers|Contact the developers]] if this error is shown for a <tt>[[$FG_ROOT]]/Nasal/</tt> script.

===Near camera not rendering===
[[Image:Near_camera_off.png|500px]]

If you screen looks like the image above; make sure you have at least [[OSG]] version 2.7.6.

===No render bin name specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===No render bin number specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===... not a valid win32 application===
This Windows error could have various reasons to pop up. Usually, the file that is causing troubles is mentioned. Re-installing this file might solve the problem.

===OBJECT_SIGN: unsupported glyph `.'===
Check the OBJECT_SIGN lines in the .stg file of the tile that was loaded when this error showed up.

===OpenAL error <AL_INVALID_VALUE>: bind source <alGenSources> Failed to generate audio source.===
This error is probably displayed because of some misdirected audio settings in the [[aircraft]]s setup. Check the -sound.xml file of the aircraft and see if all files refered to really exist. If not, try to contact the author of the plane, so he can fix the problem in the [[FlightGear CVS|CVS]] version or solve the problem yourself and let someone commit the patch.

===OpenAL error (AL_INVALID_VALUE): constructor (alBufferData) Fatal error: Failed to buffer data.===
Disabling sound is a temporarily solution for this problem.

===osgDB ac3d reader: could not find texture...===
See [[#Failed to open file ...|Failed to open file ...]]

===osgDB ac3d reader: detected surface with less than 3 vertices!===
In one of the loaded models a non-existing surface is found. This can be a single line (sometimes used to simulate thin wires) or a fault in the model.

===Program's vertex attrib binding ..., usrAttr...===
Tells you that an effect binded certain attributes to a [[Shaders|shader]].

===QNAN===
(Q)NAN stands for (Quiet) Not A Number, produced by 0/0 or other floating point break downs. There can be various causes for this:
* Using a "flap start" value of 0 in the [[YASim]] [[FDM]]. Use some small value like 0.001 instead.

===Scaling image...===
This means a texture, whether in the scenery on your aircraft or anyone elses (when multiplayer is enabled), is not sized to powers of two. All textures in FlightGear have to be sized to power of two (eg. 16*16, 32*64, 32*1024). As of version 1.9 textures are resized automaticly, but it does slow your computer down, so it's better to resize the noted textures.

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

===The system cannot find the file specified===
If you are running Windows Vista; start by looking in <tt>C:\Users\Owner\AppData\Local\VirtualStore</tt> and seeing if you have a folder called FlightGear in there. If you do, cut-and-paste (merge) that one with <tt>C:\Program Files\Flightgear</tt> and try to launch FlightGear again.

'''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible.

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

===Traffic manager could not find airport===
There is either an airport missing from apt.dat, or there is a wrong ICAO code in a [[Interactive Traffic#Building Traffic Files|traffic file]]. An airport missing from apt.dat could be due to a recent opening.

===Unable to choose requested pixel format===
Error should be solved as of version 1.9. If not, try changing your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] and/or resolution.

===Unable to find airport details for .... in FGTower::Init()===
This error can be surpressed by disabling [[Interactive Traffic|AI Traffic]], via the AI/ATC [[menu]].

The error appears when an airport in <tt>[[$FG_ROOT]]/Airports/apt.dat.gz</tt> cannot be found in <tt>[[$FG_ROOT]]/ATC/default.tower</tt> and <tt>[[$FG_ROOT]]/ATC/default.atis</tt>. Renaming the airports in the apt.dat.gz file ór in both default ATC files will fix the problem.

===Unable to open aircraft directory===
The [[aircraft]] that you are trying to run most likely relies on another aircraft, which you did not install (yet). The error shows what aircraft, so go download that one!
=== Unexpected tag '...' found in YASim aircraft description===
FlightGear found a non-existing tag in the [[FDM]] of the aircraft you are trying to launch. If you have not changed the original aircraft, contact the aircraft author. Else, check the FDM througly for mistakes.

Also, make sure you didn't force a FDM to be loaded.
* '''Commandline:''' <tt>--fdm=...</tt> should be left out.
* '''[[FGRun]]:''' <tt>Advanced > Flight Model</tt> should be set to jsb (which will leave the whole command out of the commandline, so you can use this setting with any FDM).

=== Unknown ... aircraft: ... defaulting to C172 ===
FlightGear is unable to load the forced [[FDM]] (set through <tt>--fdm=...</tt> or via <tt>Advanced > Flight Model</tt> in [[FGRun]]) for this aircraft. FlightGear automatically picks the right FDM for each aircraft, so there is no need to set it manually, unless you know what you are doing. In the Flight Model dialog of FGRun, set the FDM to <tt>jsb</tt>; that is the "auto setting".

===Unknown exception to the main loop. Aborting... Possible cause: No such file or directory===
This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear_Launch_Control#Debugging|log level]] to debug and repeating excactly what you did when the error came up, might provide some more information on what FlightGear was doing when the error occurred.
* Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work.
* Changing the resolution to a smaller one might work as well.

===WARNING: Couldn't convert texture...===
You are trying to run an aircraft not compatible with your FlightGear version. Most of the time, this error appears when you fly an aircraft, textured with .png files on versions older than 1.9. Convert the textures manually to .rgb or upgrade your FlightGear version.

===Warning: Could not find plugin to read objects from file ...===
A library is missing from your computer. Therefore, certain fileformats cannot be read. Try to reinstall/update [[OSG]], as the libraries used by FlightGear should be part of the standard package.

===Warning: Picked up TriangleIntersect===
Reduce your [[FlightGear Launch Control#Debugging|Log Level]] to alert. Or [[Showstoppers|send the fgfs output to /dev/null (unix systems) or 2>nul (Windows)]]. The errors might still be shown, but do not affect the sim anymore.

===Warning: TangentSpaceGenerator: unknown primitive mode 9===
This is an [[OSG]] error, showing up when an effect needs tangent vectors, but polygons are not support. The error itself can be ignored, altough some [[shaders]] may look wrong. Shader developers should try to minimise the use of polygons and use triangles and quads instead.

===YASim SOLUTION FAILURE: Solution failed to converge after 10000 iterations===
Some control in the [[YASim]] [[FDM]] is too weak, according to YASim, to control the aircraft. An effectiveness tag will be required in the FDM to solve this error.

===YASim SOLUTION FAILURE: Zero length fuselage===
There is a problem in the [[FDM]]. A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.

===FGMultiplayerMgr::Open - Failed to bind receive socket===

This means FlightGear was unable to open the listening network socket required by the --multiplay=in option. Frequently this option can be omitted and FlightGear will figure out the necessary parameters automatically.
Common reasons are:
* Address given in the option does not resolve to one of the IP addresses of the local machine. This parameter should only be required if you want to fine-tune the network behavior. Omitting it directs FlightGear to listen on all local interfaces automatically. Example:
--multiplay=in,10,,5001
Notice that you still need the comma.
* The UDP port given in the option (or the default port 5000 if no option given) is already in use. Verify nothing is using the port.

==Errors without known solutions==
Please take a look at the upcoming errors and see if you know a solution to get rid of them. Your additions are greatly appreciated!

===Aircraft propulsion element has problems in file ...===

===AL Error (fx): Invalid Value at pitch and gain===
The sound effect's pitch (high or low) and gain (volume multiplication factor) values are not valid.

===AL Error (sound manager): Invalid Operation at update===

===AL Error (sound manager): Invalid Value at buffer add data No such buffer!===

===Failed to execute command nasal===

===Failed to tie (or untie while closing) property ... to object methods===
A JSBSim error.

===FGMultiplayMgr::MP_ProcessData - message from ... has invalid length!===

===FGMultiplayMgr::MP_ProcessData: Result too large===

===GPS: malformed route, index=1===

===Mesa 7.3 implementation error: bad texture level in r300UploadSubImage===
http://www.flightgear.org/forums/viewtopic.php?f=2&t=6706&start=0&st=0&sk=t&sd=a

===Nasal runtime error: stack overflow===

===No image file for texture, using white===
A [[Shaders|shader]] error, possibly you (or the developer) have/has not specified a texture for a surface while modeling the aircraft model in AC3D, Blender, Wings...

===No path in /sim/sound/path===
You (or the developer) have/has not specified a proper sound file in the aircraft's -set.xml file.

===OBJECT_SIGN: unexpected } in sign contents===

===OpenAL error (AL_ILLEGAL_COMMAND): set_source_pos===

Has something to do with OpenAL not understanding where the sound comes from.

===OpenAL error (AL_ILLEGAL_COMMAND): set_volume===

Has something to do with OpenAL not understanding the sound volume.

===PT_vs_hpt: ran out of layers===
This is issued from the atmosphere implementation in FlightGear's environment system. A comment in the code says: "''should never get here''". Please provide input when this happens: excessive altitudes? Negative altitudes?

===Tried to initialize a non-existent engine!===

===Unknown Chunk: ***UNKNOWN*** (0xA08A)===

===Warning: detected OpenGL error 'invalid value' after RenderBin::draw(,)===
This warning is generated from OSG. Set your environment variable
OSG_NOTIFY_LEVEL=FATAL

===Warning: GraphicsWindowWin32::grabFocus() - Failed grabbing the focus===
It seems that this happens when you have another window open and you are "focusing" (the window is active) on it. FlightGear will try to grab itself infront of the other window.

===WARNING: PUI: Too many live puInterfaces open at once!===
Appears when printing large outputs (very) frequently on the screen.

===Warning: State::drawQuads(0, 154400) too large handle in remapping to ushort glDrawElements===

[[Category:Howto|Console output]]

[[fr:Howto: Débarrassez-vous des erreurs les plus fréquentes]]

Howto:Multiplayer

2010-12-27T21:52:43Z

Airbird1: /* Using the Windows launcher / fgrun */

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

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

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

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

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

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

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

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

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

To confirm that it's working, you can go to the multiplayer map at; http://mpmap02.flightgear.org/ (in Hong Kong). Once FlightGear has started, you will notice chat messages that say "Hello" indicating pilots that are online and then as they join (You can edit a certain configuration file to change the message, instead of "Hello", which may become boring after a while). You may wish to use a different server (i.e. "Hostname" entry).

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

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

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

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

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

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

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

--multiplay=in,10,,5000

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Related content==
* [[FlightGear Multiplayer Server]]
* [[Howto: Set up a multiplayer server]]
* [[Multiplayer protocol]]

[[Category:Howto|Multiplayer]]

[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[nl:Howto: Multiplayer]]
[[pl: Konfiguracja trybu multiplayer]]

TerraSync

2010-12-27T21:32:58Z

Airbird1: re-defined UDP

To see the terrain below your aircraft, you have to install the respective [[scenery]]. This can happen by downloading certain bits of scenery before flying as described in the article [[Installing Scenery]].

Alternatively you can use '''TerraSync'''. It is a utility that automatically downloads the newest version of the needed [[FlightGear]] [[scenery]] while the simulator is running. TerraSync runs in the background in a separate process, monitors your position, and downloads (or updates) the latest greatest scenery from the master scenery server "just in time".

The master repository for terrasync, i.e. the online resource from which TerraSync downloads its files, is synchronized with the [http://scenemodels.flightgear.org/ FlightGear Scenery Database] once a day. So when using TerraSync, you will always have 1) the latest [[File_Formats#.2A.stg|.stg-files]], which tell FlightGear where to place an object and 2) the latest '''static''' scenery objects. Static scenery objects are such objects that exist in one place only.

: <s>Important note: TerraSync does not download the newest '''shared''' scenery objects.</s> Shared objects are such objects that are used more than once in the scenery, like generic houses or ships etc. <s>If the set of shared scenery objects has changed since your version of FlightGear was released (usually that is the case), you need to install the newest [http://scenemodels.flightgear.org/download/SharedModels.tgz '''shared''' models archive] from the [http://scenemodels.flightgear.org/ FlightGear Scenery Database] to see all objects. Unpack it to <code>[FG_ROOT]\data\Models</code>.</s>
: See also: [[Howto:_Animated_jetways#Usage]]

It is recommended to use a separate scenery directory for TerraSync (i.e. do not run it on your main scenery directory) as network interruptions may upset the synchronization protocol - if/when that happens the easiest solution is to delete the affected subdirectory and let terrasync download it again.

===Usage example (for POSIX compliant [[command line]] shell)===

Start terrasync:

<code>% nice terrasync -p 5500 -S -d "$HOME/fgfsScenery"</code>

The -S option tells terrasync to use the SVN protocol to fetch data. If you omit it terrasync will use the rsync program instead (which has to be installed on your system).

Start FlightGear:

<code>% fgfs --atlas=socket,out,1,localhost,5500,udp --fg-scenery="$FG_ROOT/Scenery/:$HOME/fgfsScenery"</code>

The full documentation and source for TerraSync is located in the FlightGear source distribution (in <code>utils/TerraSync/</code>).

===Start TerraSync from fgrun.exe (Wizard in Windows) in FlightGear 1.9.1===

1. Make sure you are in the first screen where you can set up directories. To get there, start fgrun.exe. You'll first be in the Aircraft selection screen, then hit "Back". You are now here:

[[Image:TerraSync 1.png]]

2. Select the destination folder for all files downloaded by terrasync. Usually the folder <code>[FG_ROOT]\terrasync</code> already exists and you only have to add it to the list (as in the above example). Insure that it is positioned '''above''' your standard scenery folder (here that is <code>FlightGear191\scenery</code>) and all other directories over which the terrasync folder is supposed to have priority. When two directories contain information for the same region, FlightGear will take the information from the directory higher in the list.

3. For TerraSync to know where to deposit the downloaded files, you have to tell the program which folder is the destination folder. In the above example, it is the 3rd in the list.

4. Finally, go to the last screen. There you have to activate TerraSync as in the following screenshot. Now TerraSync should work.

[[Image:TerraSync 2.png]]

''Note: Expect your firewall to block in first place, since you request a new port (5505) in UDP (User Datagram Protocol)'' .

See [[Installing Scenery]]

[[Category:Software]]

Howto:Multiplayer

2010-12-27T21:24:15Z

Airbird1: /* Using the Windows launcher / fgrun */ (You can edit a certain configuration file to change the message, instead of "Hello", which may become boring after a while)

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

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

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

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

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

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

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

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

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

To confirm that it's working, you can go to the multiplayer map at; http://mpmap02.flightgear.org/ (in Hong Kong). You will notice chat messages that say "Hello" indicating pilots that are online and then as they join (You can edit a certain configuration file to change the message, instead of "Hello", which may become boring after a while). You may wish to use a different server (i.e. "Hostname" entry).

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

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

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

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

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

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

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

--multiplay=in,10,,5000

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Related content==
* [[FlightGear Multiplayer Server]]
* [[Howto: Set up a multiplayer server]]
* [[Multiplayer protocol]]

[[Category:Howto|Multiplayer]]

[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[nl:Howto: Multiplayer]]
[[pl: Konfiguracja trybu multiplayer]]

Problematic video cards

2010-12-26T08:29:23Z

Airbird1: /* Intel */ Non-GMA

{{Stub}}

''This is meant to become a list of those video cards that are known to frequently cause issues trying to run FlightGear due to having insufficient capabilities or driver support to properly run FlightGear, please feel free to help maintain this page by adding new entries or updating existing ones'''.

When building a new system or buying hardware for a computer that is specifically intended to run FlightGear, it seems like a good idea to avoid these cards and instead check out [[Hardware Recommendations]] or more specifically [[Supported Video Cards]].

Please note that even if you have one of these models, you may still be able to run FlightGear by disabling certain features, please check the forums for advice.
So, if you manage to run FlightGear with any of the cards listed here, please do feel free to update this page and preferably also list any relevant customizations or configuration settings that need to be applied.

= ATI =
* Most ATI Cards have problems running FlightGear. One ATI card that is known to work OK, is the ATI Radeon x1600, with the latest drivers.
* ATI Mobility Radeon [http://flightgear.org/forums/viewtopic.php?f=2&t=2866&p=25018&hilit=intel+gma#p25013]

= Intel GMA=
The following models of Intel GMA cards have often been found to have insufficient OpenGL support to make use of FlightGear's more recent and advanced features (such as shaders):
* Intel GMA 945
* Intel GMA 950
* Intel GMA 965
* Intel GMA 3000
* Intel GMA X3100

== Other Intel ==
Non-GMA cards can be posted here, these are most often found on lower-end PCs and laptops/notebooks.

* Mobile Intel 4 Series Express Chipset Family

Boeing 747-400 Tutorial

2010-12-20T02:11:24Z

Airbird1: /* Approach and landing */

{{Main article|Boeing 747-400}}

Pleae note that this document reflects the current status of the [http://code.google.com/p/flightgear747-400/source/checkout development (SVN) version] of the [[Boeing 747-400]] for [[FlightGear]]. Certain parts won't work or differently with older versions.

== Normal procedures guide ==
=== Preflight ===
In order to start our preflight checks, we need some power. As we will need some extra time to get confident with the flightdeck, we will use the battery. With the battery alone, we will be provided with basic power for about 30 minutes, which should be enough for us to set up a better power source.

'''Turn the BATTERY switch to ON'''. You will notice that it has a protective cover, click it to open/close it. The battery should remain on at all time, as it acts as a backup for some vital avionics, so let us close it after setting it to ON.

'''Set the BUS TIE switches to AUTO'''. This will allow power to flow propertly through all electrical systems. Set the GEN CONT switches to ON, to allow our engines' generators to provide power to the systems. It is perfectly normal for the OFF lights to be lit at thi time, it just indicates that the generators are not being used at the moment (engines are off), but that they will be used once the engines are started.

Without any engine or APU running, the best way of obtaining longterm power is through external power sources, usually provided by the groundstaff at the airport. Using external power is "cheap", as it does not require the aircraft to burn any fuel.

'''Turn ON EXT PWR 1 and, if available, EXT PWR 2'''. You will find the switches on the electrical panel on the overhead. External power is only available when you are on the ground and the parking brake is set. It can take a couple of seconds till the EXT PWR switches to ON.

Any time the aircraft is powered, nav lights should be enabled, to alert the groundcrew that the aircraft is powered and under control. So '''turn ON the NAV LIGHTS''', which can be found in the lower right part of the overhead panel. Logo and wing lights are optional, but prefered at night.

Ensure that all flight controls are centered and/or in their idle positions. Meaning '''flaps are UP, gear handle in DOWN position.'''

'''Set all fuel XFEED (crossfeed) switches to ON'''. This will distribute fuel between the main fuel tanks (there are four of them on a 747).

'''Disable NACELLE and WING ANTI-ICE'''. Nacelle anti-ice should only be enabled after the engines are started. Wing anti-ice should only be enabled after takeoff.

'''Rotate the APU switch to START''' (click twice). The switch will rotate back to ON and the APU will be started (this will take several seconds). As soon as AVAIL is displayed on the APU GEN witches, set them to ON (once again this will take a while). The APU has now taken over the job of power source from the battery, which we must leave switched on!

Press the INIT REF button on one of the CDUs on the pedestal. Then click the button next to TAKEOFF. Type the flap setting you will be using on takeoff, making use of the digits pad, then press the button next to the flap setting (upper left side button). Flap 20 is the standard flaps setting for takeoffs in the 747. You can also use flaps 10, but it will take longer for you to get airborne. '''Write down or remember your V2 speed''', as we will need this number in a moment.

'''Turn the F/D (Flight Director) ON.''' When the autopilot is on, the Flight Director is what controls where your plane goes. When the autopilot is off, the F/D will give us visual cues as to climb pitch and bank angle to keep the aircraft flying safely.

Enter V2 speed into the IAS/MACH indicator on the dashboard. You can adjust the autopilot indicator numbers by clicking the appropriate knob with your left mouse button (to increase value) or middle/3rd mouse button (to lower value). '''Currently you need to use the Autopilot > Autopilot Settings menu dialog!''' My FMC reported a V2 speed of 144 knots, so I have entered 144 into the IAS/MACH indicator. Immediately after takeoff, you will use aircraft pitch to maintain this speed.

'''Arm LNAV and VNAV''' by clicking on their respective buttons on the MCP. LNAV will control the lateral movement of the aircraft (i.e., follow your flight plan direction) and VNAV will control the vertical movement of the aircraft (get you to your cruise altitude and back down efficiently and safely). At this time we are only arming these autopilot functions. They will not actually control the aircraft until the autopilot is engages after we are airborne.

'''Set HDG to the heading of the takeoff runway.'''

'''Set ALT to 10000.''' You would typically set this to your initial cleared altitude as given by ATC. 10,000 feet will work nicely for most flights.

'''Ensure the autopilot DISENGAGE bar is UP.'''

'''Ensure that fuel control switches are set at CUTOFF''' (knobs pulled out and down). This will ensure that fuel will not flow to the engines

'''Set AUTOBRAKES to RTO.''' This will initiate full braking if something goes wrong during your takeoff roll and you reject (decide to end) the takeoff. Rejected Take Off braking WILL stop the plane VERY quickly if things go badly before you takeoff.

'''Ensure that the SEATBELTS selector is set to AUTO.''' AUTO will turn off the SEATBELT indicator when you are above 10,000 feet.

=== Pushback and start ===
'''Ensure all throttles are at idle.'''

'''Turn ON continuous ignition.''' This will send a continual spark to the engines which will ignite the fuel when it is introduced.

'''Pull the Engine Start Selector for Engine 4.'''

Watch the N2% RPM increase in the EICAS display. Bleed air from the APU is being 'blown' across the engine and is beginning to turn the turbines. '''When the N2% RPM indicator on the EICAS reaches around 14%, switch the Fuel Control Switch for Engine 4 to RUN.''' The engine should start up and then idle back.

'''Repeat this process for engine 1.''' Pull the Start Selector, wait for N2 to reach the magenta line, set Fuel Control to RUN.

'''Now do the same thing for engines 2 and 3.''' As soon as you get the hang of it, you can start engines 1 & 4 and engines 2 & 3 simultaneously.

'''Turn OFF the APU.''' The main engines are now powering the electrical, pneumatic, and hydraulic systems. The APU is no longer needed.

'''Check the upper EICAS (center display) for any warnings.''' If any appear, resolve them before continuing.

=== Taxi and Takeoff ===
Turn TAXI LIGHT ON. Even though it's daytime, it's good practice to turn them on as it makes your aircraft more visible.

'''Set flaps to takeoff configuration.''' The standard for a 747 is flaps 20, but if you set flaps 10 in the FMC earlier on, use 10. The flaps take a minute or so to extend, so extend them well before you begin your takeoff roll.

'''Move the control wheel and the control column to full travel''' in both directions and verify:
• freedom of movement
• that the controls return to center
Altough control surface failures are currently not simulated, it is good to get used to this, as you will/should do it with whatever aircraft you fly.

'''Release parking brake and taxi to the runway.''' As you taxi, review your V1, Vr, and V2 speeds. Ensure all other flight systems are set and you're ready to fly. When the runway is clear of incoming traffic, '''taxi onto the runway and stop''' (called "position and hold").

'''Turn LANDING and STROBE lights ON.'''

'''Arm Autothrottle.''' This will arm the autothrottles of the aircraft for the takeoff.

'''Ensure that F/D is ON, runway heading is set in HDG, IAS is set to V2, LNAV and VNAV are armed, and that altitude is 10,000.''' If all is set, then you're ready to fly!

'''Move throttles slowly forward to around 70% N1, then click the TO/GA button.'''

The TO/GA (Take Off/Go Around) button tells the flight computer to control throttle settings during takeoff and initial climbout. The TO/GA button is located on the yoke in the real cockpit. In FlightGear, this button is not yet implemented, press the SPD button on the glareshield instead.

Apply slight forward pressure on the stick/yoke until you reach around 80 knots to keep the nose gear firmly against the runway. Use rudder to keep the plane centered on the runway. If something goes wrong or you receive an EICAS warning message, quickly return throttles to idle and initiate reverse thrust (Delete key). Autobraking will commence if you are travelling over 85 knots, otherwise apply braking, exit the runway, resolve the problem, and try again.

'''When the copilot announces V1, this means that you're going to fly, or at least try to''', if you experience any problems. You are now going too fast to safely reject the takeoff. Any problems that you encounter should be taken into flight with you.

'''At Rotate, slowly and smoothly pull back on the controls to become airborne.''' You should be leaving the runway by the time V2 is announced.

=== Climb and cruise ===
'''As soon as you're over 500 feet altitude, select one of the A/P ENGAGE buttons''' on the autopilot MCP.

This switches LNAV and VNAV from armed to active. The autopilot is now flying the plane and you can sit back, complete this checklist, and monitor the flight.

You'll notice that as the flight continues that the autopilot will control altitude, speed, and direction.

Monitor the autopilot and speed as the aircraft levels off at 10,000 feet.

'''Turn off the TAXI and LANDING LIGHTS.'''
'''The SEATBELTS indicator may be turned off above 10,000 feet.''' If set to AUTO, it will automatically turn off.

'''Set MCP ALT to your cruise altitude and hit the center of the ALT dial''' to command the autopilot to climb.

=== Approach and landing ===
'''Set AUTOBRAKES.'''

'''Set the HDG to the runway heading. Do not press the SEL button!''' Simply enter the HDG as a reference and as a set altitude in case you abort the landing.

'''Click the INIT REF button''' on the CDU. You will see the APPROACH REF page. This page gives us two flap settings, with their corresponding speeds, that can be used for approach. Flaps 25 is the standard approach flaps setting.

'''Click LSK 1R''' to copy the flaps 25 settings and VREF speed to the scratchpad.

'''Click LSK 4R''' to set the approach flap and approach speed. This will allows the autopilot and flight director to provide accurate flap restriction speeds on approach. Take note of the approach speed value as we will need it in a few moments.

'''As soon as you begin the turn at the VCV VOR (base leg) or your descent, set the IAS/SPEED to approach speed + 5 knots.''' The approach speed is the speed referenced in the FMC previously. In order to set the speed, you must first click the center of the speed adjustment knob and then set the speed to the correct setting. The plane will now begin to decellerate to the indicated speed.

'''Use speedbrakes to slow you''' to your flaps 1 speed if your speed remains high (due to a steep descent) or if your speed exceeds 250 knots below 10,000 feet. You want to be close to your approach speed as you turn to final.

'''Lower the landing gear.''' The landing gear CAN be extended when your speed is below 270 knots and SHOULD be lowered when you set flaps 20. If you are approaching the turn to final and your speed is well above approach speed and below 270 knots, lower the gear to increase drag and help slow you down. Make sure you are at your approach speed with flaps at 25 when you are several miles from the runway.

'''ARM the speedbrake.''' With the speedbrake armed, it will deploy as soon as the main gears touch the runway.

'''Turn LANDING and TAXI lights ON.'''

Ensure that flaps are at 25, the gear is down, and that the plane is properly following the ILS. Sit back and enjoy the autolanding. The autopilot will fully control all aspects of the aircraft until touchdown. If you'd rather land manually, you can disengage the autopilot by pulling down on the DISENGAGE bar, turning A/T ARM off, and setting F/D to OFF. You will then have full control over throttle, pitch, and roll. Manually keep your speed at approach speed + 5 knots and follow the ILS indicators to the runway.

'''As the main wheels touch the ground, bring the throttles to idle and then engage full thrust reversers''' (Delete key). The autopilot will perform a rollout maneuver that will keep the aircraft centered on the runway. Braking is also performed automatically, though engaging thrust reversers will decrease brake heating and wear. Do not touch the controls except to engage thrust reversers - the plane will do everything else.

'''At 80 knots, set throttle back to idle, disengaging thrust reversers.'''

As soon as, or shortly before, the aircraft comes to a complete stop, '''DISENGAGE autopilot, set A/T ARM to OFF, and turn the F/D OFF.''' The aircraft is now in your control and you may begin your taxi. When you apply taxi thrust, the speedbrakes will retract. Exit the runway when able and taxi toward the gate or parking area of your choice. The airport here is HUGE, so you've got plenty of time to work through the remainder of the checklists.

=== Taxi in, parking, and shutdown ===
'''Set flaps to UP.'''

'''Set AUTOBRAKES to OFF.'''

'''Set LANDING and STROBE lights to OFF.'''

'''START the APU.''' This will allow us to turn off the engines, but still power the aircraft until ground power is available.

'''Set the parking brake''' as soon as you're fully stopped at the gate or parking area of your choice.

'''Turn ON APU GEN 1 and APU GEN 2.'''

'''Set FUEL control switches to CUTOFF.''' This will turnoff the engines.

'''Turn OFF the seatbelt indicator.''' This indicates that the passengers may now deplane.

'''Turn OFF the BEACON lights''' to indicate that the plane is properly parked and will not be moving. This alerts ground crew that they are free to connect ground power and unload baggage, etc.

Ground power should now be available. However, ground power is not available at all airports. You would typically switch to ground power and turn off the APU at this time, but if ground power is not available, leave the APU on to power the aircraft until you're done with the shutdown checklist.

'''Turn OFF CONT ignition.'''
'''Turn OFF AUTOSTART.'''
'''Open all XFEEDs.''' This allows fuel to flow freely if the aircraft is refueled on the ground.
'''Turn OFF APU GEN 1 and GEN 2''' (if on)
'''Turn OFF the APU''' (if running)
'''Turn OFF EXT PWR 1 and 2''' (if available)
'''Set all internal and external lighting to OFF.'''
'''Turn off the BATTERY.'''

The aircraft is now in the same cold and dark condition that it was in when we boarded. Congratulations on completing the flight!
== References ==
* http://smithplanet.com/fs2004/pmdg/
* ''747-469/-4F6 Flight Crew Operations Manual'', The Boeing Company

Boeing 747-400 Tutorial

2010-12-20T02:09:28Z

Airbird1: /* Taxi and Takeoff */

{{Main article|Boeing 747-400}}

Pleae note that this document reflects the current status of the [http://code.google.com/p/flightgear747-400/source/checkout development (SVN) version] of the [[Boeing 747-400]] for [[FlightGear]]. Certain parts won't work or differently with older versions.

== Normal procedures guide ==
=== Preflight ===
In order to start our preflight checks, we need some power. As we will need some extra time to get confident with the flightdeck, we will use the battery. With the battery alone, we will be provided with basic power for about 30 minutes, which should be enough for us to set up a better power source.

'''Turn the BATTERY switch to ON'''. You will notice that it has a protective cover, click it to open/close it. The battery should remain on at all time, as it acts as a backup for some vital avionics, so let us close it after setting it to ON.

'''Set the BUS TIE switches to AUTO'''. This will allow power to flow propertly through all electrical systems. Set the GEN CONT switches to ON, to allow our engines' generators to provide power to the systems. It is perfectly normal for the OFF lights to be lit at thi time, it just indicates that the generators are not being used at the moment (engines are off), but that they will be used once the engines are started.

Without any engine or APU running, the best way of obtaining longterm power is through external power sources, usually provided by the groundstaff at the airport. Using external power is "cheap", as it does not require the aircraft to burn any fuel.

'''Turn ON EXT PWR 1 and, if available, EXT PWR 2'''. You will find the switches on the electrical panel on the overhead. External power is only available when you are on the ground and the parking brake is set. It can take a couple of seconds till the EXT PWR switches to ON.

Any time the aircraft is powered, nav lights should be enabled, to alert the groundcrew that the aircraft is powered and under control. So '''turn ON the NAV LIGHTS''', which can be found in the lower right part of the overhead panel. Logo and wing lights are optional, but prefered at night.

Ensure that all flight controls are centered and/or in their idle positions. Meaning '''flaps are UP, gear handle in DOWN position.'''

'''Set all fuel XFEED (crossfeed) switches to ON'''. This will distribute fuel between the main fuel tanks (there are four of them on a 747).

'''Disable NACELLE and WING ANTI-ICE'''. Nacelle anti-ice should only be enabled after the engines are started. Wing anti-ice should only be enabled after takeoff.

'''Rotate the APU switch to START''' (click twice). The switch will rotate back to ON and the APU will be started (this will take several seconds). As soon as AVAIL is displayed on the APU GEN witches, set them to ON (once again this will take a while). The APU has now taken over the job of power source from the battery, which we must leave switched on!

Press the INIT REF button on one of the CDUs on the pedestal. Then click the button next to TAKEOFF. Type the flap setting you will be using on takeoff, making use of the digits pad, then press the button next to the flap setting (upper left side button). Flap 20 is the standard flaps setting for takeoffs in the 747. You can also use flaps 10, but it will take longer for you to get airborne. '''Write down or remember your V2 speed''', as we will need this number in a moment.

'''Turn the F/D (Flight Director) ON.''' When the autopilot is on, the Flight Director is what controls where your plane goes. When the autopilot is off, the F/D will give us visual cues as to climb pitch and bank angle to keep the aircraft flying safely.

Enter V2 speed into the IAS/MACH indicator on the dashboard. You can adjust the autopilot indicator numbers by clicking the appropriate knob with your left mouse button (to increase value) or middle/3rd mouse button (to lower value). '''Currently you need to use the Autopilot > Autopilot Settings menu dialog!''' My FMC reported a V2 speed of 144 knots, so I have entered 144 into the IAS/MACH indicator. Immediately after takeoff, you will use aircraft pitch to maintain this speed.

'''Arm LNAV and VNAV''' by clicking on their respective buttons on the MCP. LNAV will control the lateral movement of the aircraft (i.e., follow your flight plan direction) and VNAV will control the vertical movement of the aircraft (get you to your cruise altitude and back down efficiently and safely). At this time we are only arming these autopilot functions. They will not actually control the aircraft until the autopilot is engages after we are airborne.

'''Set HDG to the heading of the takeoff runway.'''

'''Set ALT to 10000.''' You would typically set this to your initial cleared altitude as given by ATC. 10,000 feet will work nicely for most flights.

'''Ensure the autopilot DISENGAGE bar is UP.'''

'''Ensure that fuel control switches are set at CUTOFF''' (knobs pulled out and down). This will ensure that fuel will not flow to the engines

'''Set AUTOBRAKES to RTO.''' This will initiate full braking if something goes wrong during your takeoff roll and you reject (decide to end) the takeoff. Rejected Take Off braking WILL stop the plane VERY quickly if things go badly before you takeoff.

'''Ensure that the SEATBELTS selector is set to AUTO.''' AUTO will turn off the SEATBELT indicator when you are above 10,000 feet.

=== Pushback and start ===
'''Ensure all throttles are at idle.'''

'''Turn ON continuous ignition.''' This will send a continual spark to the engines which will ignite the fuel when it is introduced.

'''Pull the Engine Start Selector for Engine 4.'''

Watch the N2% RPM increase in the EICAS display. Bleed air from the APU is being 'blown' across the engine and is beginning to turn the turbines. '''When the N2% RPM indicator on the EICAS reaches around 14%, switch the Fuel Control Switch for Engine 4 to RUN.''' The engine should start up and then idle back.

'''Repeat this process for engine 1.''' Pull the Start Selector, wait for N2 to reach the magenta line, set Fuel Control to RUN.

'''Now do the same thing for engines 2 and 3.''' As soon as you get the hang of it, you can start engines 1 & 4 and engines 2 & 3 simultaneously.

'''Turn OFF the APU.''' The main engines are now powering the electrical, pneumatic, and hydraulic systems. The APU is no longer needed.

'''Check the upper EICAS (center display) for any warnings.''' If any appear, resolve them before continuing.

=== Taxi and Takeoff ===
Turn TAXI LIGHT ON. Even though it's daytime, it's good practice to turn them on as it makes your aircraft more visible.

'''Set flaps to takeoff configuration.''' The standard for a 747 is flaps 20, but if you set flaps 10 in the FMC earlier on, use 10. The flaps take a minute or so to extend, so extend them well before you begin your takeoff roll.

'''Move the control wheel and the control column to full travel''' in both directions and verify:
• freedom of movement
• that the controls return to center
Altough control surface failures are currently not simulated, it is good to get used to this, as you will/should do it with whatever aircraft you fly.

'''Release parking brake and taxi to the runway.''' As you taxi, review your V1, Vr, and V2 speeds. Ensure all other flight systems are set and you're ready to fly. When the runway is clear of incoming traffic, '''taxi onto the runway and stop''' (called "position and hold").

'''Turn LANDING and STROBE lights ON.'''

'''Arm Autothrottle.''' This will arm the autothrottles of the aircraft for the takeoff.

'''Ensure that F/D is ON, runway heading is set in HDG, IAS is set to V2, LNAV and VNAV are armed, and that altitude is 10,000.''' If all is set, then you're ready to fly!

'''Move throttles slowly forward to around 70% N1, then click the TO/GA button.'''

The TO/GA (Take Off/Go Around) button tells the flight computer to control throttle settings during takeoff and initial climbout. The TO/GA button is located on the yoke in the real cockpit. In FlightGear, this button is not yet implemented, press the SPD button on the glareshield instead.

Apply slight forward pressure on the stick/yoke until you reach around 80 knots to keep the nose gear firmly against the runway. Use rudder to keep the plane centered on the runway. If something goes wrong or you receive an EICAS warning message, quickly return throttles to idle and initiate reverse thrust (Delete key). Autobraking will commence if you are travelling over 85 knots, otherwise apply braking, exit the runway, resolve the problem, and try again.

'''When the copilot announces V1, this means that you're going to fly, or at least try to''', if you experience any problems. You are now going too fast to safely reject the takeoff. Any problems that you encounter should be taken into flight with you.

'''At Rotate, slowly and smoothly pull back on the controls to become airborne.''' You should be leaving the runway by the time V2 is announced.

=== Climb and cruise ===
'''As soon as you're over 500 feet altitude, select one of the A/P ENGAGE buttons''' on the autopilot MCP.

This switches LNAV and VNAV from armed to active. The autopilot is now flying the plane and you can sit back, complete this checklist, and monitor the flight.

You'll notice that as the flight continues that the autopilot will control altitude, speed, and direction.

Monitor the autopilot and speed as the aircraft levels off at 10,000 feet.

'''Turn off the TAXI and LANDING LIGHTS.'''
'''The SEATBELTS indicator may be turned off above 10,000 feet.''' If set to AUTO, it will automatically turn off.

'''Set MCP ALT to your cruise altitude and hit the center of the ALT dial''' to command the autopilot to climb.

=== Approach and landing ===
'''Set AUTOBRAKES.'''

'''Set the HDG to the runway heading.''' Do not press the SEL button. Simply enter the HDG as a reference and as a set altitude in case you abort the landing.

'''Click the INIT REF button''' on the CDU. You will see the APPROACH REF page. This page gives us two flap settings, with their corresponding speeds, that can be used for approach. Flaps 25 is the standard approach flaps setting.

'''Click LSK 1R''' to copy the flaps 25 settings and VREF speed to the scratchpad.

'''Click LSK 4R''' to set the approach flap and approach speed. This will allows the autopilot and flight director to provide accurate flap restriction speeds on approach. Take note of the approach speed value as we will need it in a few moments.

'''As soon as you begin the turn at the VCV VOR (base leg) or your descent, set the IAS/SPEED to approach speed + 5 knots.''' The approach speed is the speed referenced in the FMC previously. In order to set the speed, you must first click the center of the speed adjustment knob and then set the speed to the correct setting. The plane will now begin to decellerate to the indicated speed.

'''Use speedbrakes to slow you''' to your flaps 1 speed if your speed remains high (due to a steep descent) or if your speed exceeds 250 knots below 10,000 feet. You want to be close to your approach speed as you turn to final.

'''Lower the landing gear.''' The landing gear CAN be extended when your speed is below 270 knots and SHOULD be lowered when you set flaps 20. If you are approaching the turn to final and your speed is well above approach speed and below 270 knots, lower the gear to increase drag and help slow you down. Make sure you are at your approach speed with flaps at 25 when you are several miles from the runway.

'''ARM the speedbrake.''' With the speedbrake armed, it will deploy as soon as the main gears touch the runway.

'''Turn LANDING and TAXI lights ON.'''

Ensure that flaps are at 25, the gear is down, and that the plane is properly following the ILS. Sit back and enjoy the autolanding. The autopilot will fully control all aspects of the aircraft until touchdown. If you'd rather land manually, you can disengage the autopilot by pulling down on the DISENGAGE bar, turning A/T ARM off, and setting F/D to OFF. You will then have full control over throttle, pitch, and roll. Manually keep your speed at approach speed + 5 knots and follow the ILS indicators to the runway.

'''As the main wheels touch the ground, bring the throttles to idle and then engage full thrust reversers''' (Delete key). The autopilot will perform a rollout maneuver that will keep the aircraft centered on the runway. Braking is also performed automatically, though engaging thrust reversers will decrease brake heating and wear. Do not touch the controls except to engage thrust reversers - the plane will do everything else.

'''At 80 knots, set throttle back to idle, disengaging thrust reversers.'''

As soon as, or shortly before, the aircraft comes to a complete stop, '''DISENGAGE autopilot, set A/T ARM to OFF, and turn the F/D OFF.''' The aircraft is now in your control and you may begin your taxi. When you apply taxi thrust, the speedbrakes will retract. Exit the runway when able and taxi toward the gate or parking area of your choice. The airport here is HUGE, so you've got plenty of time to work through the remainder of the checklists.

=== Taxi in, parking, and shutdown ===
'''Set flaps to UP.'''

'''Set AUTOBRAKES to OFF.'''

'''Set LANDING and STROBE lights to OFF.'''

'''START the APU.''' This will allow us to turn off the engines, but still power the aircraft until ground power is available.

'''Set the parking brake''' as soon as you're fully stopped at the gate or parking area of your choice.

'''Turn ON APU GEN 1 and APU GEN 2.'''

'''Set FUEL control switches to CUTOFF.''' This will turnoff the engines.

'''Turn OFF the seatbelt indicator.''' This indicates that the passengers may now deplane.

'''Turn OFF the BEACON lights''' to indicate that the plane is properly parked and will not be moving. This alerts ground crew that they are free to connect ground power and unload baggage, etc.

Ground power should now be available. However, ground power is not available at all airports. You would typically switch to ground power and turn off the APU at this time, but if ground power is not available, leave the APU on to power the aircraft until you're done with the shutdown checklist.

'''Turn OFF CONT ignition.'''
'''Turn OFF AUTOSTART.'''
'''Open all XFEEDs.''' This allows fuel to flow freely if the aircraft is refueled on the ground.
'''Turn OFF APU GEN 1 and GEN 2''' (if on)
'''Turn OFF the APU''' (if running)
'''Turn OFF EXT PWR 1 and 2''' (if available)
'''Set all internal and external lighting to OFF.'''
'''Turn off the BATTERY.'''

The aircraft is now in the same cold and dark condition that it was in when we boarded. Congratulations on completing the flight!
== References ==
* http://smithplanet.com/fs2004/pmdg/
* ''747-469/-4F6 Flight Crew Operations Manual'', The Boeing Company

Boeing 747-400 Tutorial

2010-12-20T02:05:45Z

Airbird1: /* Taxi and Takeoff */ Enable the autothrottle --> arm the autothrottle

{{Main article|Boeing 747-400}}

Pleae note that this document reflects the current status of the [http://code.google.com/p/flightgear747-400/source/checkout development (SVN) version] of the [[Boeing 747-400]] for [[FlightGear]]. Certain parts won't work or differently with older versions.

== Normal procedures guide ==
=== Preflight ===
In order to start our preflight checks, we need some power. As we will need some extra time to get confident with the flightdeck, we will use the battery. With the battery alone, we will be provided with basic power for about 30 minutes, which should be enough for us to set up a better power source.

'''Turn the BATTERY switch to ON'''. You will notice that it has a protective cover, click it to open/close it. The battery should remain on at all time, as it acts as a backup for some vital avionics, so let us close it after setting it to ON.

'''Set the BUS TIE switches to AUTO'''. This will allow power to flow propertly through all electrical systems. Set the GEN CONT switches to ON, to allow our engines' generators to provide power to the systems. It is perfectly normal for the OFF lights to be lit at thi time, it just indicates that the generators are not being used at the moment (engines are off), but that they will be used once the engines are started.

Without any engine or APU running, the best way of obtaining longterm power is through external power sources, usually provided by the groundstaff at the airport. Using external power is "cheap", as it does not require the aircraft to burn any fuel.

'''Turn ON EXT PWR 1 and, if available, EXT PWR 2'''. You will find the switches on the electrical panel on the overhead. External power is only available when you are on the ground and the parking brake is set. It can take a couple of seconds till the EXT PWR switches to ON.

Any time the aircraft is powered, nav lights should be enabled, to alert the groundcrew that the aircraft is powered and under control. So '''turn ON the NAV LIGHTS''', which can be found in the lower right part of the overhead panel. Logo and wing lights are optional, but prefered at night.

Ensure that all flight controls are centered and/or in their idle positions. Meaning '''flaps are UP, gear handle in DOWN position.'''

'''Set all fuel XFEED (crossfeed) switches to ON'''. This will distribute fuel between the main fuel tanks (there are four of them on a 747).

'''Disable NACELLE and WING ANTI-ICE'''. Nacelle anti-ice should only be enabled after the engines are started. Wing anti-ice should only be enabled after takeoff.

'''Rotate the APU switch to START''' (click twice). The switch will rotate back to ON and the APU will be started (this will take several seconds). As soon as AVAIL is displayed on the APU GEN witches, set them to ON (once again this will take a while). The APU has now taken over the job of power source from the battery, which we must leave switched on!

Press the INIT REF button on one of the CDUs on the pedestal. Then click the button next to TAKEOFF. Type the flap setting you will be using on takeoff, making use of the digits pad, then press the button next to the flap setting (upper left side button). Flap 20 is the standard flaps setting for takeoffs in the 747. You can also use flaps 10, but it will take longer for you to get airborne. '''Write down or remember your V2 speed''', as we will need this number in a moment.

'''Turn the F/D (Flight Director) ON.''' When the autopilot is on, the Flight Director is what controls where your plane goes. When the autopilot is off, the F/D will give us visual cues as to climb pitch and bank angle to keep the aircraft flying safely.

Enter V2 speed into the IAS/MACH indicator on the dashboard. You can adjust the autopilot indicator numbers by clicking the appropriate knob with your left mouse button (to increase value) or middle/3rd mouse button (to lower value). '''Currently you need to use the Autopilot > Autopilot Settings menu dialog!''' My FMC reported a V2 speed of 144 knots, so I have entered 144 into the IAS/MACH indicator. Immediately after takeoff, you will use aircraft pitch to maintain this speed.

'''Arm LNAV and VNAV''' by clicking on their respective buttons on the MCP. LNAV will control the lateral movement of the aircraft (i.e., follow your flight plan direction) and VNAV will control the vertical movement of the aircraft (get you to your cruise altitude and back down efficiently and safely). At this time we are only arming these autopilot functions. They will not actually control the aircraft until the autopilot is engages after we are airborne.

'''Set HDG to the heading of the takeoff runway.'''

'''Set ALT to 10000.''' You would typically set this to your initial cleared altitude as given by ATC. 10,000 feet will work nicely for most flights.

'''Ensure the autopilot DISENGAGE bar is UP.'''

'''Ensure that fuel control switches are set at CUTOFF''' (knobs pulled out and down). This will ensure that fuel will not flow to the engines

'''Set AUTOBRAKES to RTO.''' This will initiate full braking if something goes wrong during your takeoff roll and you reject (decide to end) the takeoff. Rejected Take Off braking WILL stop the plane VERY quickly if things go badly before you takeoff.

'''Ensure that the SEATBELTS selector is set to AUTO.''' AUTO will turn off the SEATBELT indicator when you are above 10,000 feet.

=== Pushback and start ===
'''Ensure all throttles are at idle.'''

'''Turn ON continuous ignition.''' This will send a continual spark to the engines which will ignite the fuel when it is introduced.

'''Pull the Engine Start Selector for Engine 4.'''

Watch the N2% RPM increase in the EICAS display. Bleed air from the APU is being 'blown' across the engine and is beginning to turn the turbines. '''When the N2% RPM indicator on the EICAS reaches around 14%, switch the Fuel Control Switch for Engine 4 to RUN.''' The engine should start up and then idle back.

'''Repeat this process for engine 1.''' Pull the Start Selector, wait for N2 to reach the magenta line, set Fuel Control to RUN.

'''Now do the same thing for engines 2 and 3.''' As soon as you get the hang of it, you can start engines 1 & 4 and engines 2 & 3 simultaneously.

'''Turn OFF the APU.''' The main engines are now powering the electrical, pneumatic, and hydraulic systems. The APU is no longer needed.

'''Check the upper EICAS (center display) for any warnings.''' If any appear, resolve them before continuing.

=== Taxi and Takeoff ===
Turn TAXI LIGHT ON. Even though it's daytime, it's good practice to turn them on as it makes your aircraft more visible.

'''Set flaps to takeoff configuration.''' The standard for a 747 is flaps 20, but if you set flaps 10 in the FMC earlier on, use 10. The flaps take a minute or so to extend, so extend them well before you begin your takeoff roll.

'''Move the control wheel and the control column to full travel''' in both directions and verify:
• freedom of movement
• that the controls return to center
Altough control surface failures are currently not simulated, it is good to get used to this, as you will/should do it with whatever aircraft you fly.

'''Release parking brake and taxi to the runway.''' As you taxi, review your V1, Vr, and V2 speeds. Ensure all other flight systems are set and you're ready to fly. When the runway is clear of incoming traffic, '''taxi onto the runway and stop''' (called "position and hold").

'''Turn LANDING and STROBE lights ON.'''

'''Arm Autothrottle.''' This will arm the autothrottles of the aircraft for the takeoff.

'''Ensure that F/D is ON, runway heading is set in HDG, IAS is set to V2, LNAV and VNAV are armed, and that altitude is 10,000.''' If all is set, then you're ready to fly!

'''Move throttles slowly forward to around 70% N1, then click the TO/GA button.'''

The TO/GA (Take Off/Go Around) button tells the flight computer to control throttle settings during takeoff and initial climbout. The TO/GA button is located on the yoke in the real cockpit. In FlightGear, this button is not yet implemented, press the SPD button on the glareshield instead.

Apply slight forward pressure on the stick/yoke until you reach around 80 knots to keep the nose gear firmly against the runway. Use rudder to keep the plane centered on the runway. If something goes wrong or you receive an EICAS warning message, quickly return throttles to idle and initiate reverse thrust (Delete key). Autobraking will commence if you are travelling over 85 knots, otherwise apply braking, exit the runway, resolve the problem, and try again.

When the copilot announces V1, this means that you're going to fly, or at least try to, if you experience any problems. You are now going too fast to safely reject the takeoff. Any problems that you encounter should be taken into flight with you.

'''At Rotate, slowly and smoothly pull back on the controls to become airborne.''' You should be leaving the runway by the time V2 is announced.

=== Climb and cruise ===
'''As soon as you're over 500 feet altitude, select one of the A/P ENGAGE buttons''' on the autopilot MCP.

This switches LNAV and VNAV from armed to active. The autopilot is now flying the plane and you can sit back, complete this checklist, and monitor the flight.

You'll notice that as the flight continues that the autopilot will control altitude, speed, and direction.

Monitor the autopilot and speed as the aircraft levels off at 10,000 feet.

'''Turn off the TAXI and LANDING LIGHTS.'''
'''The SEATBELTS indicator may be turned off above 10,000 feet.''' If set to AUTO, it will automatically turn off.

'''Set MCP ALT to your cruise altitude and hit the center of the ALT dial''' to command the autopilot to climb.

=== Approach and landing ===
'''Set AUTOBRAKES.'''

'''Set the HDG to the runway heading.''' Do not press the SEL button. Simply enter the HDG as a reference and as a set altitude in case you abort the landing.

'''Click the INIT REF button''' on the CDU. You will see the APPROACH REF page. This page gives us two flap settings, with their corresponding speeds, that can be used for approach. Flaps 25 is the standard approach flaps setting.

'''Click LSK 1R''' to copy the flaps 25 settings and VREF speed to the scratchpad.

'''Click LSK 4R''' to set the approach flap and approach speed. This will allows the autopilot and flight director to provide accurate flap restriction speeds on approach. Take note of the approach speed value as we will need it in a few moments.

'''As soon as you begin the turn at the VCV VOR (base leg) or your descent, set the IAS/SPEED to approach speed + 5 knots.''' The approach speed is the speed referenced in the FMC previously. In order to set the speed, you must first click the center of the speed adjustment knob and then set the speed to the correct setting. The plane will now begin to decellerate to the indicated speed.

'''Use speedbrakes to slow you''' to your flaps 1 speed if your speed remains high (due to a steep descent) or if your speed exceeds 250 knots below 10,000 feet. You want to be close to your approach speed as you turn to final.

'''Lower the landing gear.''' The landing gear CAN be extended when your speed is below 270 knots and SHOULD be lowered when you set flaps 20. If you are approaching the turn to final and your speed is well above approach speed and below 270 knots, lower the gear to increase drag and help slow you down. Make sure you are at your approach speed with flaps at 25 when you are several miles from the runway.

'''ARM the speedbrake.''' With the speedbrake armed, it will deploy as soon as the main gears touch the runway.

'''Turn LANDING and TAXI lights ON.'''

Ensure that flaps are at 25, the gear is down, and that the plane is properly following the ILS. Sit back and enjoy the autolanding. The autopilot will fully control all aspects of the aircraft until touchdown. If you'd rather land manually, you can disengage the autopilot by pulling down on the DISENGAGE bar, turning A/T ARM off, and setting F/D to OFF. You will then have full control over throttle, pitch, and roll. Manually keep your speed at approach speed + 5 knots and follow the ILS indicators to the runway.

'''As the main wheels touch the ground, bring the throttles to idle and then engage full thrust reversers''' (Delete key). The autopilot will perform a rollout maneuver that will keep the aircraft centered on the runway. Braking is also performed automatically, though engaging thrust reversers will decrease brake heating and wear. Do not touch the controls except to engage thrust reversers - the plane will do everything else.

'''At 80 knots, set throttle back to idle, disengaging thrust reversers.'''

As soon as, or shortly before, the aircraft comes to a complete stop, '''DISENGAGE autopilot, set A/T ARM to OFF, and turn the F/D OFF.''' The aircraft is now in your control and you may begin your taxi. When you apply taxi thrust, the speedbrakes will retract. Exit the runway when able and taxi toward the gate or parking area of your choice. The airport here is HUGE, so you've got plenty of time to work through the remainder of the checklists.

=== Taxi in, parking, and shutdown ===
'''Set flaps to UP.'''

'''Set AUTOBRAKES to OFF.'''

'''Set LANDING and STROBE lights to OFF.'''

'''START the APU.''' This will allow us to turn off the engines, but still power the aircraft until ground power is available.

'''Set the parking brake''' as soon as you're fully stopped at the gate or parking area of your choice.

'''Turn ON APU GEN 1 and APU GEN 2.'''

'''Set FUEL control switches to CUTOFF.''' This will turnoff the engines.

'''Turn OFF the seatbelt indicator.''' This indicates that the passengers may now deplane.

'''Turn OFF the BEACON lights''' to indicate that the plane is properly parked and will not be moving. This alerts ground crew that they are free to connect ground power and unload baggage, etc.

Ground power should now be available. However, ground power is not available at all airports. You would typically switch to ground power and turn off the APU at this time, but if ground power is not available, leave the APU on to power the aircraft until you're done with the shutdown checklist.

'''Turn OFF CONT ignition.'''
'''Turn OFF AUTOSTART.'''
'''Open all XFEEDs.''' This allows fuel to flow freely if the aircraft is refueled on the ground.
'''Turn OFF APU GEN 1 and GEN 2''' (if on)
'''Turn OFF the APU''' (if running)
'''Turn OFF EXT PWR 1 and 2''' (if available)
'''Set all internal and external lighting to OFF.'''
'''Turn off the BATTERY.'''

The aircraft is now in the same cold and dark condition that it was in when we boarded. Congratulations on completing the flight!
== References ==
* http://smithplanet.com/fs2004/pmdg/
* ''747-469/-4F6 Flight Crew Operations Manual'', The Boeing Company

Template talk:Under Construction

2010-12-03T18:21:09Z

Airbird1: Reply

We already have a relatively widely-used [[Template:WIP|"Work in Progress" template]], so is this one really necessary?

[[User:Skyop|Skyop]] 05:42, 2 December 2010 (UTC)

* I just think of it as nice alternative, because WIP sort of covers cleanup of existing articles, and Under Construction covers new articles.

[[User:Airbird1|Airbird1]] 18:21, 3 December 2010 (UTC)

Template:Under Construction

2010-12-02T04:41:28Z

Airbird1:

{| class=toccolours style="text-align: center; width: 100%; font-size: 100%; clear:both; margin-top:1em; margin-bottom:-0.5em;"
| [[File:Construction sign.jpg]] '''This article is under construction and is not ready for use. Please [{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} contribute to this article] if you can. Discuss the article's progress on the [[Template_talk:{{PAGENAME}}|talk page]].'''
|}

<noinclude>This template marks articles as under construction.</noinclude>

Template:Under Construction

2010-12-02T04:41:01Z

Airbird1: Edited talk page link

{| class=toccolours style="text-align: center; width: 100%; font-size: 100%; clear:both; margin-top:1em; margin-bottom:-0.5em;"
| [[File:Construction sign.jpg]] '''This article is under construction and is not ready for use. Please [{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} contribute to this article] if you can. Discuss the article's progress on the [[Template_talk:{{PAGENAME}}|talk page]].'''.
|}

<noinclude>This template marks articles as under construction.</noinclude>

Template:Under Construction

2010-12-02T04:37:48Z

Airbird1: Added construction sign, talk page link

{| class=toccolours style="text-align: center; width: 100%; font-size: 100%; clear:both; margin-top:1em; margin-bottom:-0.5em;"
| [[File:Construction sign.jpg]] '''This article is under construction and is not ready for use. Please [{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} contribute to this article] if you can. Discuss the article's progress on the [{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=talk}} talk page]'''.
|}

<noinclude>This template marks articles as under construction.</noinclude>

File:Construction sign.jpg

2010-12-02T04:32:56Z

Airbird1: Used in the template Template:Under Construction, do not remove unless template removed.

Used in the template Template:Under Construction, do not remove unless template removed.

Help:Templates

2010-12-02T04:24:35Z

Airbird1: /* User messages */ Added Under Construction Template

This page is meant to help you with the use of '''templates''' on the wiki.

==User messages==
{| border=1 cellpadding=3 style="border: 1px #AAAAAA solid; border-collapse: collapse;background:#ffffff;"
|- style="background:#eeeeee;"
! width="20%" | Tag
! width="70%" | Text that will be shown
! width="10%" | Place
|-
|<nowiki>{{abc}}</nowiki>
|{{abc}}
|Top
|-
|<nowiki>{{afd}}</nowiki>
|{{afd}}
|Top
|-
|<nowiki>{{Boeing}}</nowiki>
|{{Boeing}}
|Bottom
|-
|<nowiki>{{Building}}</nowiki>
|{{Building}}
|Bottom
|-
|<nowiki>{{cleanup}}</nowiki>
|{{cleanup}}
|Top
|-
|<nowiki>{{non-stable}}</nowiki>
|{{non-stable}}
|Top
|-
|<nowiki>{{Main article|Link to article}}</nowiki>
|{{Main article|Link to article}}
|
|-
|<nowiki>{{merge|page}}</nowiki>
|{{merge|page}}
|Top
|-
|<nowiki>{{mergefrom|page}}</nowiki>
|{{mergefrom|page}}
|Top
|-
|<nowiki>{{mergeto|page}}</nowiki>
|{{mergeto|page}}
|Top
|-
|<nowiki>{{mergedisputed|page}}</nowiki>
|{{mergedisputed|page}}
|Top
|-
|<nowiki>{{split-multiple}}</nowiki>
|{{split-multiple}}
|Top
|-
|<nowiki>{{stub}}</nowiki>
|{{stub}}
|Top
|-
|<nowiki>{{Under Construction}}</nowiki>
|{{Under Construction}}
|Top
|}

==Infoboxes==
===Aircraft===
{{infobox Aircraft
|image =A380.jpg
|name =Airbus A380
|type =Airliner
|livery =British Airways, Emirates Airline, Singapore Airlines
|authors = Ampere K.
|fdm =JSBSim
|status =Under development
|fgname =<tt>A380</tt>
}}
{{-}}

===Airport===
{{infobox Airport
|name = Amsterdam Airport Schiphol
|image =EHAM.jpg
|alt =Schiphol in the [[FlightGear NL]] scenery
|iata =AMS
|icao =EHAM
|type =public
|owner =Schiphol Group
|city =Amsterdam, The Netherlands
|runway= 18R/36L
|length= 3800 m
|material= Asfalt
|runway2= 06/24
|length2= 3490 m
|material2=Asfalt
|website =http://www.schiphol.nl
}}
{{-}}

===User===
{{User
|name = Jack
|location = New York, United States
|age = 21
|job = Pilot
|interests = FlightGear, Computers, Aircraft
|callsign = jackie
|favourite =[[Boeing 747-400]], [[Cessna C172]]
|website =[http://www.jp.flightgear.org http://www.jp.flightgear.org]
}}

[[Category:Help]]

Template:Under Construction

2010-12-02T04:21:42Z

Airbird1: Created Template:Under Construction

{| class=toccolours style="text-align: center; width: 100%; font-size: 100%; clear:both; margin-top:1em; margin-bottom:-0.5em;"
| '''This article is under construction and is not ready for use. Please [{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} contribute to this article] if you can.'''.
|}

<noinclude>This template marks articles as under construction.</noinclude>

User:Airbird1

2010-12-02T02:50:53Z

Airbird1: /* My Page */ Hawker Sea Hawk FGA.6

=My Page=
{{User
|name = Airbird1
|location = Coquitlam, B.C., Canada
|interests = FlightGear, Computers, Aircraft, Space, Astronomy
|callsign = Airbird1, MOBIL1, KOAK_TWR or _CTR
|favourite =[[Airbus A340-600]], [[KC-135]], [[F-16]], [[Hawker Sea Hawk FGA.6]]
}}

== My Callsigns: ==

* ATC, Services, and AAR
** MOBIL1 (KC-135)
** KOAK_CTR (Always atc-tower)
** KOAK_TWR (Always atc-tower)

* Aircraft
** Airbird1 (A340-600, Other planes)

== About Me ==

Location: Coquitlam, BC, Canada

Favourite Airport: CYVR (Vancouver Intl.)

Favourite Planes: A340-600, KC-135, X-15

System:

Windows 7 Home Premium
Intel Celeron CPU 2.2 Ghz
64 Bit Edition with 32 Bit support
TOSHIBA Satellite C655 Laptop
Suckish graphics, average 6 frames per second

FG Version: 2.0.0, no CVS, no Git

== Virtual Pilotage Skill ==

* Knows IFR Flight and VFR Flight
* A bit rusty on ILS skills.
* Able to traverse a maze of NDBs, VORs, and fixes.
* GPS Hugger
* Likes to do low flyovers at 250 feet above KSFO in a KC-135, just to freakout whoever's tower.

== Other Stuff ==

Title is self-explanatory. Oddball tidbits are coming soon.

777tutoriaILSksfo-klax l

2010-11-29T00:40:39Z

Airbird1: moved 777tutoriaILSksfo-klax l to 777-200ER ILS Tutorial KSFO-KLAX: 777tutorialILSksfo-klax l is a bad title.

#REDIRECT [[777-200ER ILS Tutorial KSFO-KLAX]]

777-200ER ILS tutorial KSFO-KLAX

2010-11-29T00:40:39Z

Airbird1: moved 777tutoriaILSksfo-klax l to 777-200ER ILS Tutorial KSFO-KLAX: 777tutorialILSksfo-klax l is a bad title.

'''''UNDER MAJOR EDITING BY AIRBIRD1'''''
{{cleanup}}

=Welcome to the Vaerospace Advanced Flightgear Tutorial=

==Your First City to City Flight==
We begin with flight planning. The first thing we have to plan is which standard departure route we need to fly and which standard high altitude route. We are going to follow... eermm actually that's in real life, for now we need to get up and level at 300-320 knots around 15,000-20,000 ft and follow the VOR (and VORTAC) beacons as specified in this tutorial. The recommended aircraft is a 777.

==Salinas NAV1 and DME set to 117.3==
Pick a runway at KSFO (San Francisco International). Recommended runway is 28R. Takeoff and do a climbing turn to heading 150 degrees. Now set NAV1 and DME to Salinas (117.3). When the DME reaches about 65 nautical miles, steer the 777 toward the needle (if the needle deviates from the 12 o'clock position you should steer slightly toward or into the needle). The needle will begin to move back toward 12 o'clock. Steering toward the needle too frequently is called chasing the needle/"bird dogging" and should be avoided.

==Paso Robales NAV2 set to 114.3==
Okay, set NAV2 (777: Be sure to switch both NAV toggle switches on the panel on and set NAV2 to 114.3, when you are approximately 20-30 DME nautical miles away from Salinas steer onto the NAV2 needle to 12 o'clock (pointing straight ahead) and set NAV1 to our next beacon (San Marcus @ 114.9) and set DME to Paso Robales 114.3. Make sure you remember which needle is for NAV1 and which is for NAV2! 777: NAV2 is the "skinny one".

==San Marcus NAV1 set to 114.9, DME Paso Robales 114.3==
Using the same strategy to avoid too much bird dogging (chasing the needle), turn onto the NAV1 needle once 20 NM DME from Paso Robales and maintain your chosen flight level and do not exceed 25,000 ft (if you're a beginner), once onroute to San Marcus immediately switch NAV2 and DME to Oxnard 108.7 and use the same procedure.

==Oxnard NAV1 and DME set to 108.7 - Coming Down ==
30 DME from Oxnard bring the aircraft down gently (no more than 150 feet per minute)
to 8000 feet and level out at 285 knots, but do not use speedbrakes. Now do a visual check. As you come into the bay area over the water, KLAX is close. Stay 4-5 NM DME out to sea, and descend to 2500 feet.

=Your All Instrument Approach - Runway 24L ILS Localizer NAV1 set to 111.7, set NAV2 to KLAX VOR 113.6=
Make sure NAV1 is set to the localizer for runway 24L (that's the leftmost runway visable from out at sea), maintaining your heading until the needle is at 10 o'clock (pointing left). Now turn the aircraft into the needle so it points forward/upright again... you should be on a heading of approx. 240 degrees.

At the bottom of the left Electronic Flight Instrument System/EFIS (Honeywell Primus 1000 EFIS) there are white markers and another white indicator will appear. If this indicator is in the centre of the marks -- there are two sets of marks, one for heading into runway and the other (verical white ticks on the right of the left screen) for pitch or glideslope. These scales and their markers should always be "Dead Center" -- if they are you are in line for your runway, and only good planning will make this so...

Head for 24L and land as usual.

To be upgraded and expanded

captain vaeron www.vaero.za.net

777-200ER ILS tutorial KSFO-KLAX

2010-11-29T00:37:05Z

Airbird1: Major cleaning

User:Airbird1

2010-11-28T23:16:29Z

Airbird1:

=My Page=
{{User
|name = Airbird1
|location = Coquitlam, B.C., Canada
|interests = FlightGear, Computers, Aircraft, Space, Astronomy
|callsign = Airbird1, MOBIL1, KOAK_TWR or _CTR
|favourite =[[Airbus A340-600]], [[KC-135]], [[F-16]]
}}

== My Callsigns: ==

* ATC, Services, and AAR
** MOBIL1 (KC-135)
** KOAK_CTR (Always atc-tower)
** KOAK_TWR (Always atc-tower)

* Aircraft
** Airbird1 (A340-600, Other planes)

== About Me ==

Location: Coquitlam, BC, Canada

Favourite Airport: CYVR (Vancouver Intl.)

Favourite Planes: A340-600, KC-135, X-15

System:

Windows 7 Home Premium
Intel Celeron CPU 2.2 Ghz
64 Bit Edition with 32 Bit support
TOSHIBA Satellite C655 Laptop
Suckish graphics, average 6 frames per second

FG Version: 2.0.0, no CVS, no Git

== Virtual Pilotage Skill ==

* Knows IFR Flight and VFR Flight
* A bit rusty on ILS skills.
* Able to traverse a maze of NDBs, VORs, and fixes.
* GPS Hugger
* Likes to do low flyovers at 250 feet above KSFO in a KC-135, just to freakout whoever's tower.

== Other Stuff ==

Title is self-explanatory. Oddball tidbits are coming soon.

Howto:Make an aircraft

2010-11-28T23:06:29Z

Airbird1: /* Before you start */ Tools of the Trade

{{stub}}

There are many things required to '''develop an [[aircraft]] for [[FlightGear]]'''. We encourage new aircraft [[Portal:Developer|developers]] to start their 'career' by modifying and enhancing existing aircraft. It is much easier to do and gives you a giant advantage by the time you create an aircraft completely by yourself.

The content in this article gives a summary of codes and can be found on most planes. So, for examples on how it's used, you can take a look at some random planes.

==Before you start==
If you are a complete beginner, knowing the processes involved will help out quite a bit. Roughly 4 simplified steps, first creating your 3d model, then the FDM, followed by creating animations and finally to implement systems. Each aircraft in FlightGear has two main development areas:
# The '''[[Flight Dynamics Model|Flight Dynamics Model]] (FDM)''': This tells the computer how your aircraft reacts to various conditions. The FDM is composed of two main models most people use, either [[JSBSim]] or [[YASim]]. Or the lesser used model [[UIUC]]. Define the dimensions, mass-and-balance data. Tell FlightGear which part of your aircraft and where it may hit the ground. Where the gear is, if and how it travels. How it is propelled and how it flies if you move the controls. A subarea of the FDM are integral systems like the [[autopilot]] and fuel systems.
# The '''appearence''' of the aircraft, which can be split in two areas:
## 3-dimensional model and all of its visual aspects: animations (These give visual feedback from your FDM. Move the aileron of your 3D model when the aileron control is moved. Same for the other aero surfaces, the gear. Than go ahead with the instruments, animate the needles, the digital readouts. Define hot spots and pick animations, so you can click in your 3D cockpit.), [[Howto: Add aircraft lights|lighting]] and textures (images that are put in specific locations on the 3D model).
## auditory (sounds).

===Rules and guidelines===
* All images in FlightGear should be sized to powers of two (eg. 64*64, 128*256 or 16*1024). Since FlightGear 1.9, images no longer have to be saved in the .rgb format. Right now .png is most common used among FlightGear developers.
* Please note that we use spaces in our codes, some developers use rather tabs, to make our code easy(er) to read. Every line that starts a new tag, we press the space key once, so you get a kind of stairs. It does not really matter what method you use, as long as you use it consistently throughout all of your files.
* Filenames and directories are case-sensitive on most OS's. Windows is not case-sensitive, so when you are developing on a Windows machine, you won't notice any problems. On other OS's, there is a difference between 'Boeing' and 'boeing'. Since FlightGear is used on multiple platforms, make sure your code makes correct usage of capitals.

===Tools of the Trade===
If you realize this is harder than you expect, don't worry. For the first-timer, the FDM(aircraft.xml), aircraft-set.xml, and the engine.xml files are the easiest. Modeling will require considerable time and practice. You want to have the tools for the job, so here are some tools to help:

* Aeromatic (works only for JSBSim, gives you entire engine file and FDM (aircraft.xml) file.
* JSBSim Commander (Only JSBSim, helps with the multitude of tags, try this on your aircraft BEFORE you release it and AFTER you are finished with all the xmls)
* This wiki
* Flightgear Forum
* Design plans and specifications of your aircraft, including:
** Three-View Plan (shows front view, top view, side view)
** Technical Specifications (from Wikipedia, Boeing, or Airbus)
** '''NOTE:''' Implement the specifications into the xmls
* A friend, and/or another developer, let's say you only want to do the FDM and XMLs. You'll need another person (a modeller) to model. Don't worry, the <author> tag has enough room. ;)
* 6 days for xmls + 2 weeks for modeling
* your patience

==Directories and files==
The data created during development results in many files, which are stored in several directories per aircraft. Each aircraft has its own directory in the <tt>$FG_ROOT/Aircraft/</tt> directory. The first thing to do when you start working on a new aircraft is to make a directory for it. A short version of the aircraft name (eg. harrier), or its serial number (eg. 747-400) is prefered. More directories might be needed further on, but we will create them when we need them. They are explained in this article, but you can skip them if you are working on your first aircraft. For now we create one directory, namely:

* <tt>Models/</tt> all files related to the appearence of the model are saved in this directory.

All paths are relative to [[$FG_ROOT]], with the exception of some that are explicit noted.

* '''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a tag is mis-matched and which tag is mis-matched, if a token/comment is not closed, and if in general something is wrong. You'll probably know there's a problem if IE displays an error message.

===The .xml file (FDM)===
This file contains the entire (or partial) [[Flight Dynamics Model]] of the aircraft. We have three different systems; they all have their up- and downsides.
* [[YASim]], needed for: helicopters, towing over a [[Howto: Multiplayer|multiplay network]]
* [[JSBSim]], needed for: [[Howto: Implement pushback|pushback]] (external forces)
* [[UIUC]] (rarely used these days)
With limited data available, YASim is generally considered to be the best way to go. When you have acces to real windtunnel data and/or require more flexibility, JSBSim might be a better choice.

===The -set.xml file===
This is the most important file of a FlightGear aircraft. This is the only file that is read directly by FlightGear. Actually it can be compared with an airport hub (from where flights of a certain airline to all other airports departure and arrive). The -set.xml file leads FlightGear to all files that are needed to simulate the aircraft. The -set.xml file should be stored in the aircrafts root directory (eg. <tt>$FG_ROOT/Aircraft/747-400/</tt>)

Most XML files in FlightGear use the so called [[PropertyList XML File|Property List]] format.
Always begin the -set.xml file with:

<PropertyList>
<sim>

and close the file with:

</sim>
</PropertyList>

The following tags are to be placed between the <sim> and </sim> tags.

====<description></description>====
The text that is to be shown in the aircraft selection dialog of [[FGRun]] and other GUIs.

====<aircraft-version>====
Commonly shows the latest update date.

====<status></status>====
The status of the development of your plane. This can for example be used in order to get a list of aircraft with a certain minimum development status by passing the --min-status= parameter to the fgfs executable.

As of 05/2009 the following status "symbols" are supported:
* alpha
* beta
* early-production
* production

====<author></author>====
Place your name(s) here. If multiple people worked on the same aircraft, you can place the specific development area for each person between ( ).

====<flight-model></flight-model>====
What FDM system is the aircraft using. Set to 'yasim' for [[YASim]] and to 'jsb' for [[JSBSim]].

====<aero></aero>====
The filename of the FDM file, without .xml. You have created this file earlier on at: [[#The .xml file (FDM)]]

====<splash-texture></splash-texture>====
Place the location of an image you would like to show during loading of the aircraft. FlightGear will randomly pick one of the generic splashes in <tt>[[$FG_ROOT]]/Textures/</tt> when this line is not found in the -set.xml file.

====<splash-title></splash-title>====
Adds small text (above the splash texture) to the loading screen.

====<model><path></path></model>====
Where to find the model. Could be an .ac file (plain model format) or .xml if you want to have extras like animations etc.

====<sound><path></path></sound>====
The path to your aircrafts sound file, do not include if you don't have one. The pitch and volume of the sound is controlled by the xml file and throttle position. If for example you find a nice wav file of the jet engine you're using, you can fix it up with your favorite sound editor so it loops nicely and include that into your model (I've noticed a few models where it can get quite annoying when the loop length is so small you can really notice it) so make it smooth.

For additional information, you'll want to check out <tt>[[$FG_ROOT]]/Docs/README.xmlsound</tt>

====<panel><path></path></panel>====
Where to find the (2D) panel. We prefer 3D cockpits, which are linked in the model .xml file.

====<autopilot><path></path></autopilot>====
Where to find the [[autopilot]] system.

===Engines/ directory===
Only required for JSBSim aircraft. In this directory the engine and thruster/propeller files are stored.

===Models/ directory===
This directory contains all model related files; such as textures, models and animation files (.xml). In the -set.xml file we've set the path to one .xml file. That file should link (indirect) to each other model file (including a possible 3D cockpit) needed for the plane. The whole plane could be modeled into one file, but most developers prefer to split things up. A cockpit for example can be built up by several files, each existing of just one [[Creating instruments for FG|instrument]] or panel. This way it is easy to (re)move certain parts of the aircraft. You set up your model file like this:

<pre>
<PropertyList>

<path>Aircraft.ac</path>

<model>
<name>Cockpit</name>
<path>Aircraft/.../Models/cockpit.xml</path>
<offsets>
<x-m> -5.25</x-m>
<y-m> 0.00</y-m>
<z-m> 1.30</z-m>
</offsets>
</model>

<animation>
<type>rotate</type>
<object-name>AileronLeft</object-name>
<property>/controls/flight/aileron</property>
<factor>-65</factor>
<center>
<x-m> 2.09</x-m>
<y-m>-5.50</y-m>
<z-m>-1.50</z-m>
</center>
<axis>
<x>1</x>
<y>0</y>
<z>0</z>
</axis>
</animation>

</PropertyList>
</pre>

The cockpit.xml file can contain a similair structure, with all the instruments as seperate models. The amount of models is not limited, nor is the amount of animations.

A detailed article about animating and models can be found in [[Howto: 3D Aircraft Models]].

A common subdirectory is the <tt>Liveries/</tt> one, which holds the livery files. See [[Livery over MP]] for more information about that subject.

===Nasal/ directory===
All [[Nasal]] code specific to the aircraft is placed in this directory, with the exception of some system or instrument specific Nasal. If a certain Nasal script is usefull for all aircraft (eg. weather or [[Howto: Multiplayer|multiplayer]] related) it can be placed in the <tt>[[$FG_ROOT]]/Nasal</tt> directory. Nasal scripts that are useable on multiple aircraft (eg. [[Howto: Air-Air Refueling|air-air refueling]]) can be found in the <tt>[[$FG_ROOT]]/Aircraft/Generic</tt> directory.

===Sounds/ directory===
What is an airliner without the sound of its mighty engines, or a glider without the sound of wind blowing around your face? Sounds are quite important to increase the feeling that you are actually into the simulation. In this directory all sound files that are specific for the aircarft are stored. Sounds that can be used on multiple aircraft (eg. the click of a switch or thunder) are available in the <tt>[[$FG_ROOT]]/Sounds</tt> directory.

===Tutorials/ directory===
A helpfull feature in learning how to start the engines of a plane, flying a basic leg etc. is FlightGears tutorial system. It allows you to create a step by step tutorial that guides the user through a certain procedure. It can even indicate what switches should be pressed!

More about the tutorial system can be found at [[Tutorials]].

==Comments in XML files==
We can place extra information in XML files, that will be ignored by FlightGear. Such as descriptions and explanations of certain XML markups, changelogs etc.

These will be mainly useful to other developers working with your XML code, for example when updating/maintaining your files, or when borrowing XML code from your work.

<pre> </pre>

==Related content==
*[[Howto: Request new aircraft]]
*[[Howto: Make a helicopter]]

[[Category:Aircraft enhancement|Make an aircraft]]
[[Category:Howto|Make an aircraft]]

Howto:Make an aircraft

2010-11-28T22:51:16Z

Airbird1: /* Directories and files */ Hint for developers

{{stub}}

There are many things required to '''develop an [[aircraft]] for [[FlightGear]]'''. We encourage new aircraft [[Portal:Developer|developers]] to start their 'career' by modifying and enhancing existing aircraft. It is much easier to do and gives you a giant advantage by the time you create an aircraft completely by yourself.

The content in this article gives a summary of codes and can be found on most planes. So, for examples on how it's used, you can take a look at some random planes.

==Before you start==
If you are a complete beginner, knowing the processes involved will help out quite a bit. Roughly 4 simplified steps, first creating your 3d model, then the FDM, followed by creating animations and finally to implement systems. Each aircraft in FlightGear has two main development areas:
# The '''[[Flight Dynamics Model|Flight Dynamics Model]] (FDM)''': This tells the computer how your aircraft reacts to various conditions. The FDM is composed of two main models most people use, either [[JSBSim]] or [[YASim]]. Or the lesser used model [[UIUC]]. Define the dimensions, mass-and-balance data. Tell FlightGear which part of your aircraft and where it may hit the ground. Where the gear is, if and how it travels. How it is propelled and how it flies if you move the controls. A subarea of the FDM are integral systems like the [[autopilot]] and fuel systems.
# The '''appearence''' of the aircraft, which can be split in two areas:
## 3-dimensional model and all of its visual aspects: animations (These give visual feedback from your FDM. Move the aileron of your 3D model when the aileron control is moved. Same for the other aero surfaces, the gear. Than go ahead with the instruments, animate the needles, the digital readouts. Define hot spots and pick animations, so you can click in your 3D cockpit.), [[Howto: Add aircraft lights|lighting]] and textures (images that are put in specific locations on the 3D model).
## auditory (sounds).

===Rules and guidelines===
* All images in FlightGear should be sized to powers of two (eg. 64*64, 128*256 or 16*1024). Since FlightGear 1.9, images no longer have to be saved in the .rgb format. Right now .png is most common used among FlightGear developers.
* Please note that we use spaces in our codes, some developers use rather tabs, to make our code easy(er) to read. Every line that starts a new tag, we press the space key once, so you get a kind of stairs. It does not really matter what method you use, as long as you use it consistently throughout all of your files.
* Filenames and directories are case-sensitive on most OS's. Windows is not case-sensitive, so when you are developing on a Windows machine, you won't notice any problems. On other OS's, there is a difference between 'Boeing' and 'boeing'. Since FlightGear is used on multiple platforms, make sure your code makes correct usage of capitals.

==Directories and files==
The data created during development results in many files, which are stored in several directories per aircraft. Each aircraft has its own directory in the <tt>$FG_ROOT/Aircraft/</tt> directory. The first thing to do when you start working on a new aircraft is to make a directory for it. A short version of the aircraft name (eg. harrier), or its serial number (eg. 747-400) is prefered. More directories might be needed further on, but we will create them when we need them. They are explained in this article, but you can skip them if you are working on your first aircraft. For now we create one directory, namely:

* <tt>Models/</tt> all files related to the appearence of the model are saved in this directory.

All paths are relative to [[$FG_ROOT]], with the exception of some that are explicit noted.

* '''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a tag is mis-matched and which tag is mis-matched, if a token/comment is not closed, and if in general something is wrong. You'll probably know there's a problem if IE displays an error message.

===The .xml file (FDM)===
This file contains the entire (or partial) [[Flight Dynamics Model]] of the aircraft. We have three different systems; they all have their up- and downsides.
* [[YASim]], needed for: helicopters, towing over a [[Howto: Multiplayer|multiplay network]]
* [[JSBSim]], needed for: [[Howto: Implement pushback|pushback]] (external forces)
* [[UIUC]] (rarely used these days)
With limited data available, YASim is generally considered to be the best way to go. When you have acces to real windtunnel data and/or require more flexibility, JSBSim might be a better choice.

===The -set.xml file===
This is the most important file of a FlightGear aircraft. This is the only file that is read directly by FlightGear. Actually it can be compared with an airport hub (from where flights of a certain airline to all other airports departure and arrive). The -set.xml file leads FlightGear to all files that are needed to simulate the aircraft. The -set.xml file should be stored in the aircrafts root directory (eg. <tt>$FG_ROOT/Aircraft/747-400/</tt>)

Most XML files in FlightGear use the so called [[PropertyList XML File|Property List]] format.
Always begin the -set.xml file with:

<PropertyList>
<sim>

and close the file with:

</sim>
</PropertyList>

The following tags are to be placed between the <sim> and </sim> tags.

====<description></description>====
The text that is to be shown in the aircraft selection dialog of [[FGRun]] and other GUIs.

====<aircraft-version>====
Commonly shows the latest update date.

====<status></status>====
The status of the development of your plane. This can for example be used in order to get a list of aircraft with a certain minimum development status by passing the --min-status= parameter to the fgfs executable.

As of 05/2009 the following status "symbols" are supported:
* alpha
* beta
* early-production
* production

====<author></author>====
Place your name(s) here. If multiple people worked on the same aircraft, you can place the specific development area for each person between ( ).

====<flight-model></flight-model>====
What FDM system is the aircraft using. Set to 'yasim' for [[YASim]] and to 'jsb' for [[JSBSim]].

====<aero></aero>====
The filename of the FDM file, without .xml. You have created this file earlier on at: [[#The .xml file (FDM)]]

====<splash-texture></splash-texture>====
Place the location of an image you would like to show during loading of the aircraft. FlightGear will randomly pick one of the generic splashes in <tt>[[$FG_ROOT]]/Textures/</tt> when this line is not found in the -set.xml file.

====<splash-title></splash-title>====
Adds small text (above the splash texture) to the loading screen.

====<model><path></path></model>====
Where to find the model. Could be an .ac file (plain model format) or .xml if you want to have extras like animations etc.

====<sound><path></path></sound>====
The path to your aircrafts sound file, do not include if you don't have one. The pitch and volume of the sound is controlled by the xml file and throttle position. If for example you find a nice wav file of the jet engine you're using, you can fix it up with your favorite sound editor so it loops nicely and include that into your model (I've noticed a few models where it can get quite annoying when the loop length is so small you can really notice it) so make it smooth.

For additional information, you'll want to check out <tt>[[$FG_ROOT]]/Docs/README.xmlsound</tt>

====<panel><path></path></panel>====
Where to find the (2D) panel. We prefer 3D cockpits, which are linked in the model .xml file.

====<autopilot><path></path></autopilot>====
Where to find the [[autopilot]] system.

===Engines/ directory===
Only required for JSBSim aircraft. In this directory the engine and thruster/propeller files are stored.

===Models/ directory===
This directory contains all model related files; such as textures, models and animation files (.xml). In the -set.xml file we've set the path to one .xml file. That file should link (indirect) to each other model file (including a possible 3D cockpit) needed for the plane. The whole plane could be modeled into one file, but most developers prefer to split things up. A cockpit for example can be built up by several files, each existing of just one [[Creating instruments for FG|instrument]] or panel. This way it is easy to (re)move certain parts of the aircraft. You set up your model file like this:

<pre>
<PropertyList>

<path>Aircraft.ac</path>

<model>
<name>Cockpit</name>
<path>Aircraft/.../Models/cockpit.xml</path>
<offsets>
<x-m> -5.25</x-m>
<y-m> 0.00</y-m>
<z-m> 1.30</z-m>
</offsets>
</model>

<animation>
<type>rotate</type>
<object-name>AileronLeft</object-name>
<property>/controls/flight/aileron</property>
<factor>-65</factor>
<center>
<x-m> 2.09</x-m>
<y-m>-5.50</y-m>
<z-m>-1.50</z-m>
</center>
<axis>
<x>1</x>
<y>0</y>
<z>0</z>
</axis>
</animation>

</PropertyList>
</pre>

The cockpit.xml file can contain a similair structure, with all the instruments as seperate models. The amount of models is not limited, nor is the amount of animations.

A detailed article about animating and models can be found in [[Howto: 3D Aircraft Models]].

A common subdirectory is the <tt>Liveries/</tt> one, which holds the livery files. See [[Livery over MP]] for more information about that subject.

===Nasal/ directory===
All [[Nasal]] code specific to the aircraft is placed in this directory, with the exception of some system or instrument specific Nasal. If a certain Nasal script is usefull for all aircraft (eg. weather or [[Howto: Multiplayer|multiplayer]] related) it can be placed in the <tt>[[$FG_ROOT]]/Nasal</tt> directory. Nasal scripts that are useable on multiple aircraft (eg. [[Howto: Air-Air Refueling|air-air refueling]]) can be found in the <tt>[[$FG_ROOT]]/Aircraft/Generic</tt> directory.

===Sounds/ directory===
What is an airliner without the sound of its mighty engines, or a glider without the sound of wind blowing around your face? Sounds are quite important to increase the feeling that you are actually into the simulation. In this directory all sound files that are specific for the aircarft are stored. Sounds that can be used on multiple aircraft (eg. the click of a switch or thunder) are available in the <tt>[[$FG_ROOT]]/Sounds</tt> directory.

===Tutorials/ directory===
A helpfull feature in learning how to start the engines of a plane, flying a basic leg etc. is FlightGears tutorial system. It allows you to create a step by step tutorial that guides the user through a certain procedure. It can even indicate what switches should be pressed!

More about the tutorial system can be found at [[Tutorials]].

==Comments in XML files==
We can place extra information in XML files, that will be ignored by FlightGear. Such as descriptions and explanations of certain XML markups, changelogs etc.

These will be mainly useful to other developers working with your XML code, for example when updating/maintaining your files, or when borrowing XML code from your work.

<pre> </pre>

==Related content==
*[[Howto: Request new aircraft]]
*[[Howto: Make a helicopter]]

[[Category:Aircraft enhancement|Make an aircraft]]
[[Category:Howto|Make an aircraft]]

Howto:Understand console output

2010-11-28T22:36:59Z

Airbird1: /* Failed to tie property ... to object methods */

This document lists '''[[FlightGear]] errors''', how to get rid of them and other '''console output'''. If FlightGear quits but does not give you any error, try increasing the [[FlightGear Launch Control#Debugging|Log Level]].

Errors can appear in various locations, but the most common one is the console (a black window), which pops up when you run fgfs.exe.

==Errors with known solutions==
===Airports/.... ... Done===
This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG_SCENERY]]/Airports</tt> directory.

===Base package check failed ... Found version [none] at: ... Please upgrade to version:===
* FlightGear was unable to find the [[$FG_ROOT]] directory. Set it using the <tt>--fg-root=</tt> commandline option.
* When using [[CVS]] with binaries, the data must match the binary. You cannot use data from a different date than the binary's release date.

===condition: comparison without property[1] or value===
A condition (like <tt><less-than></tt> or <tt><equals></tt>) exists, without either:
* a property to check
* a value to check the property against

===Could not find at least one of the following objects for animation:===
This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. If you are not the aircraft's author you can safely ignore such warnings.

===creating 3D noise texture... DONE===
Tells you that a new noise texture is created. It is not an error and can be ignored.

===Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified====
Try changing the [[FlightGear Launch Control#Page Four - Options and Run|BPP]] value of your FlightGear setup. If that does not work, your graphics card is probably not able to run FlightGear 1.9 and higher. Another graphics card, or an older FlightGear version will likely "fix" the problem.

===Error: bind() failed in make_server_socket()===
When using [[Howto: Multiplayer|multiplayer]] or socket input, this usually means you specified an invalid ip address or the port is in use. Note: for multiplayer, you don't need to use the ''--multiplay=in,...'' option at all, FlightGear (since version 1.0) figures out the proper setting automatically. Only use when you know what you are doing.

===Error Building Technique: findAttr: could not find attribute bool===
Make sure that your data and source (or binary) match. They must be from the same date, to provide the best performance.

===Error: connect() failed in make_client_socket() SG_IO_OUT socket creation failed===
Your computer is not connected with the internet.

===Error: RenderTexture requires the following unsupported OpenGL extensions...===
Your graphics card doesn't support some graphics feature that FG requires. Update your drivers, change the BPP value and/or try disabling some of the visual goodies like [[3D Clouds]].

===Failed to find .... in apt.dat.gz===
You need to edit ATC/default.tower and ATC/default.atis. You can open these files with any text editor. Either remove or fix the entries containing your airports ICAO code (like KSFO).

===Failed to locate aircraft carrier = ...===
FlightGear is unable to find a [[Aircraft carrier|carrier]] under the set name. Check your commandline (<tt>--carrier=...</tt>) or the [[FlightGear Launch Control#Page Three - Airport Selection|airport page]] of the launcher.

'''Hint:''' Make sure your park position and carrier name is correct. See the [[Howto: Carrier|wiki's carrier page]] for details.

===Failed to open file ...===
Check if the file exists on your system. If the missing file is a scenery object; be sure you have the latest [http://scenemodels.flightgear.org/download/SharedModels.tgz Shared Models] from the [[FlightGear Scenery Database]].

===Fatal error: mismatched tag ...===
In some .xml file, an opening tag (like <tt><sim></tt>) does not match its closing tag (like <tt></sim></tt>). This error is hard to track down, best method is to comment (place code between <nowiki></nowiki>) most of the aircraft. Then uncomment code one by one, until the error appears again.

'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a tag is mis-matched and which tag is mis-matched. You'll probably know there's a problem if IE displays an error message.

===Fatal error: name must begin with alpha or '_'===
This error comes up when a property should be formed of which the name does not start with a letter of the alphabet or _. If this error only happens with certain planes, contact their authors.

===Fatal error: unclosed token===
A token (<nowiki></nowiki>) has been started, but not closes. Add <nowiki>--></nowiki> at the correct line.

'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a comment/token is not closed.

===FGMultiplayMgr::MP_ProcessData: No such file or directory===
This is telling you that there's someone online on the multiplayerserver, using a plane that you do not have installed on your own system. In order to remove the error (and see the other plane) you have to install the plane that the other pilot is using.

===FGMultiplayMgr - No receiver port, Multiplayermode disabled===
FlightGear [[Howto: Multiplayer|multiplayer]] has not been set.

===FGPropertyManager::GetNode() No node found for ... In component: ... unknown property ... referenced. Aborting===
FlightGear found a reference in the [[FDM]] to a non-existing property.

===FGPropertyManager::GetNode() No node found for ... The property ... is undefined.===
FlightGear found a reference in the [[FDM]] to a non-existing property. Keep in mind that JSBSim reads the FDM from top to bottom. Properties should always be created before they are needed somewhere.

===Fgtzfile_read(): : Invalid argument Fatal error: Timezone reading failed===
This one is caused by wrong line ending in a timezone file. Solution might be to download the Timezone/time.tab file manually from [http://gitorious.org/fg/fgdata/blobs/raw/master/Timezone/zone.tab Gitorious] (Right mouseclick > Save target as) and overwrite the file in <tt>[[$FG_ROOT]]/Timezone/time.tab</tt> with it.

===Found unexpected subsystem: system exiting. JSBSim failed to load aircraft and/or engine model===
You are probably trying to run an aircraft on a out-of-date version of FlightGear. The planes on the official download page are intended to be used with the latest version of FlightGear. Usage on any older systems may not work.

===freeglut (fgfs): Unable to create direct context rendering for window 'FlightGear' This may hurt performance===
This reports that you do not have proper hardware accelerated 3D (direct rendering) configured.

===Gate ... doesn't seem to have routes associated with it===
A startup location in the [[Interactive Traffic#Ground networks|groundnetwork]] is not (properly) connected to a taxi route. Contact the airport author, or import the network to [[TaxiDraw]] and run the Verify network command to find the corrupted gate.

===glLinkProgram "" Failed===
Update your drivers; they have to support atleast OpenGL 2.0 for FlightGear 2.0 and later.

===loading scenario '...'===
This is not an error. It shows that an [[AI Systems#AI Models|AI scenario]] is loaded.

===Model not found: ...===
This one tells you that FlightGear was unable to find a certain file. The nice thing is that it also tells you excactly what file.

# Check if the file really does not exist at your computer.
# Try to locate the file in which the missing file is referenced. This is likely to be <tt>-set.xml</tt> in the root directory of the loaded [[aircraft]]. Between the <model> tags, the base model file is referenced. This file references to all other models that are displayed with the aircraft.
# Contact the aircraft author with a detailed bug-report, in which you state the excact location of the missing file and (if you found it) the file in which it is referenced.

===Nasal runtime error: nil used in numeric context===
This error is [[Nasal]] triggered by a Nasal file (the console should show what file (and line) and from where it was referenced). The Nasal script tried to do something with a [[Property Tree|property]] with an empty value. A solution is to fill the property before the Nasal is loaded. This can be done by setting the property in an [[aircraft]]'s <tt>-set.xml</tt> file or by adding a [[Nasal scripting language#Listeners and Signals|listener]] to the script.

[[Howto: Contact the developers|Contact the developers]] if this error is shown for a <tt>[[$FG_ROOT]]/Nasal/</tt> script.

===Near camera not rendering===
[[Image:Near_camera_off.png|500px]]

If you screen looks like the image above; make sure you have at least [[OSG]] version 2.7.6.

===No render bin name specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===No render bin number specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===... not a valid win32 application===
This Windows error could have various reasons to pop up. Usually, the file that is causing troubles is mentioned. Re-installing this file might solve the problem.

===OBJECT_SIGN: unsupported glyph `.'===
Check the OBJECT_SIGN lines in the .stg file of the tile that was loaded when this error showed up.

===OpenAL error <AL_INVALID_VALUE>: bind source <alGenSources> Failed to generate audio source.===
This error is probably displayed because of some misdirected audio settings in the [[aircraft]]s setup. Check the -sound.xml file of the aircraft and see if all files refered to really exist. If not, try to contact the author of the plane, so he can fix the problem in the [[FlightGear CVS|CVS]] version or solve the problem yourself and let someone commit the patch.

===OpenAL error (AL_INVALID_VALUE): constructor (alBufferData) Fatal error: Failed to buffer data.===
Disabling sound is a temporarily solution for this problem.

===osgDB ac3d reader: could not find texture...===
See [[#Failed to open file ...|Failed to open file ...]]

===osgDB ac3d reader: detected surface with less than 3 vertices!===
In one of the loaded models a non-existing surface is found. This can be a single line (sometimes used to simulate thin wires) or a fault in the model.

===Program's vertex attrib binding ..., usrAttr...===
Tells you that an effect binded certain attributes to a [[Shaders|shader]].

===QNAN===
(Q)NAN stands for (Quiet) Not A Number, produced by 0/0 or other floating point break downs. There can be various causes for this:
* Using a "flap start" value of 0 in the [[YASim]] [[FDM]]. Use some small value like 0.001 instead.

===Scaling image...===
This means a texture, whether in the scenery on your aircraft or anyone elses (when multiplayer is enabled), is not sized to powers of two. All textures in FlightGear have to be sized to power of two (eg. 16*16, 32*64, 32*1024). As of version 1.9 textures are resized automaticly, but it does slow your computer down, so it's better to resize the noted textures.

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

===The system cannot find the file specified===
If you are running Windows Vista; start by looking in <tt>C:\Users\Owner\AppData\Local\VirtualStore</tt> and seeing if you have a folder called FlightGear in there. If you do, cut-and-paste (merge) that one with <tt>C:\Program Files\Flightgear</tt> and try to launch FlightGear again.

'''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible.

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

===Traffic manager could not find airport===
There is either an airport missing from apt.dat, or there is a wrong ICAO code in a [[Interactive Traffic#Building Traffic Files|traffic file]]. An airport missing from apt.dat could be due to a recent opening.

===Unable to choose requested pixel format===
Error should be solved as of version 1.9. If not, try changing your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] and/or resolution.

===Unable to find airport details for .... in FGTower::Init()===
This error can be surpressed by disabling [[Interactive Traffic|AI Traffic]], via the AI/ATC [[menu]].

The error appears when an airport in <tt>[[$FG_ROOT]]/Airports/apt.dat.gz</tt> cannot be found in <tt>[[$FG_ROOT]]/ATC/default.tower</tt> and <tt>[[$FG_ROOT]]/ATC/default.atis</tt>. Renaming the airports in the apt.dat.gz file ór in both default ATC files will fix the problem.

===Unable to open aircraft directory===
The [[aircraft]] that you are trying to run most likely relies on another aircraft, which you did not install (yet). The error shows what aircraft, so go download that one!
=== Unexpected tag '...' found in YASim aircraft description===
FlightGear found a non-existing tag in the [[FDM]] of the aircraft you are trying to launch. If you have not changed the original aircraft, contact the aircraft author. Else, check the FDM througly for mistakes.

Also, make sure you didn't force a FDM to be loaded.
* '''Commandline:''' <tt>--fdm=...</tt> should be left out.
* '''[[FGRun]]:''' <tt>Advanced > Flight Model</tt> should be set to jsb (which will leave the whole command out of the commandline, so you can use this setting with any FDM).

=== Unknown ... aircraft: ... defaulting to C172 ===
FlightGear is unable to load the forced [[FDM]] (set through <tt>--fdm=...</tt> or via <tt>Advanced > Flight Model</tt> in [[FGRun]]) for this aircraft. FlightGear automatically picks the right FDM for each aircraft, so there is no need to set it manually, unless you know what you are doing. In the Flight Model dialog of FGRun, set the FDM to <tt>jsb</tt>; that is the "auto setting".

===Unknown exception to the main loop. Aborting... Possible cause: No such file or directory===
This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear_Launch_Control#Debugging|log level]] to debug and repeating excactly what you did when the error came up, might provide some more information on what FlightGear was doing when the error occurred.
* Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work.
* Changing the resolution to a smaller one might work as well.

===WARNING: Couldn't convert texture...===
You are trying to run an aircraft not compatible with your FlightGear version. Most of the time, this error appears when you fly an aircraft, textured with .png files on versions older than 1.9. Convert the textures manually to .rgb or upgrade your FlightGear version.

===Warning: Could not find plugin to read objects from file ...===
A library is missing from your computer. Therefore, certain fileformats cannot be read. Try to reinstall/update [[OSG]], as the libraries used by FlightGear should be part of the standard package.

===Warning: Picked up TriangleIntersect===
Reduce your [[FlightGear Launch Control#Debugging|Log Level]] to alert. Or [[Showstoppers|send the fgfs output to /dev/null (unix systems) or 2>nul (Windows)]]. The errors might still be shown, but do not affect the sim anymore.

===Warning: TangentSpaceGenerator: unknown primitive mode 9===
This is an [[OSG]] error, showing up when an effect needs tangent vectors, but polygons are not support. The error itself can be ignored, altough some [[shaders]] may look wrong. Shader developers should try to minimise the use of polygons and use triangles and quads instead.

===YASim SOLUTION FAILURE: Solution failed to converge after 10000 iterations===
Some control in the [[YASim]] [[FDM]] is too weak, according to YASim, to control the aircraft. An effectiveness tag will be required in the FDM to solve this error.

===YASim SOLUTION FAILURE: Zero length fuselage===
There is a problem in the [[FDM]]. A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.

===FGMultiplayerMgr::Open - Failed to bind receive socket===

This means FlightGear was unable to open the listening network socket required by the --multiplay=in option. Frequently this option can be omitted and FlightGear will figure out the necessary parameters automatically.
Common reasons are:
* Address given in the option does not resolve to one of the IP addresses of the local machine. This parameter should only be required if you want to fine-tune the network behavior. Omitting it directs FlightGear to listen on all local interfaces automatically. Example:
--multiplay=in,10,,5001
Notice that you still need the comma.
* The UDP port given in the option (or the default port 5000 if no option given) is already in use. Verify nothing is using the port.

==Errors without known solutions==
Please take a look at the upcoming errors and see if you know a solution to get rid of them. Your additions are greatly appreciated!

===AL Error (fx): Invalid Value at pitch and gain===

===AL Error (sound manager): Invalid Operation at update===

===AL Error (sound manager): Invalid Value at buffer add data No such buffer!===

===Failed to execute command nasal===

===Failed to tie (or untie while closing) property ... to object methods===
A JSBSim error.

===FGMultiplayMgr::MP_ProcessData - message from ... has invalid length!===

===FGMultiplayMgr::MP_ProcessData: Result too large===

===GPS: malformed route, index=1===

===Mesa 7.3 implementation error: bad texture level in r300UploadSubImage===
http://www.flightgear.org/forums/viewtopic.php?f=2&t=6706&start=0&st=0&sk=t&sd=a

===Nasal runtime error: stack overflow===

===No image file for texture, using white===
A [[Shaders|shader]] error, possibly you (or the developer) have/has not specified a texture for a surface while modeling the aircraft model in AC3D, Blender, Wings...

===No path in /sim/sound/path===

You (or the developer) have/has not specified a proper sound file in the aircraft's -set.xml file.

===OBJECT_SIGN: unexpected } in sign contents===

===OpenAL error (AL_ILLEGAL_COMMAND): set_source_pos===

Has something to do with OpenAL not understanding where the sound comes from.

===OpenAL error (AL_ILLEGAL_COMMAND): set_volume===

Has something to do with OpenAL not understanding the sound volume.

===PT_vs_hpt: ran out of layers===
This is issued from the atmosphere implementation in FlightGear's environment system. A comment in the code says: "''should never get here''". Please provide input when this happens: excessive altitudes? Negative altitudes?

===Warning: detected OpenGL error 'invalid value' after RenderBin::draw(,)===
This warning is generated from OSG. Set your environment variable
OSG_NOTIFY_LEVEL=FATAL

===Warning: GraphicsWindowWin32::grabFocus() - Failed grabbing the focus===

It seems that this happens when you have another window open and you are "focusing" (the window is active) on it. FlightGear will try to grab itself infront of the other window.

===WARNING: PUI: Too many live puInterfaces open at once!===
Appears when printing large outputs (very) frequently on the screen.

===Warning: State::drawQuads(0, 154400) too large handle in remapping to ushort glDrawElements===

[[Category:Howto|Get rid of common errors]]

[[fr:Howto: Débarrassez-vous des erreurs les plus fréquentes]]

Howto:Understand console output

2010-11-28T22:32:43Z

Airbird1: /* Fatal error: unclosed token */ Hint for Developers

This document lists '''[[FlightGear]] errors''', how to get rid of them and other '''console output'''. If FlightGear quits but does not give you any error, try increasing the [[FlightGear Launch Control#Debugging|Log Level]].

Errors can appear in various locations, but the most common one is the console (a black window), which pops up when you run fgfs.exe.

==Errors with known solutions==
===Airports/.... ... Done===
This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG_SCENERY]]/Airports</tt> directory.

===Base package check failed ... Found version [none] at: ... Please upgrade to version:===
* FlightGear was unable to find the [[$FG_ROOT]] directory. Set it using the <tt>--fg-root=</tt> commandline option.
* When using [[CVS]] with binaries, the data must match the binary. You cannot use data from a different date than the binary's release date.

===condition: comparison without property[1] or value===
A condition (like <tt><less-than></tt> or <tt><equals></tt>) exists, without either:
* a property to check
* a value to check the property against

===Could not find at least one of the following objects for animation:===
This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. If you are not the aircraft's author you can safely ignore such warnings.

===creating 3D noise texture... DONE===
Tells you that a new noise texture is created. It is not an error and can be ignored.

===Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified====
Try changing the [[FlightGear Launch Control#Page Four - Options and Run|BPP]] value of your FlightGear setup. If that does not work, your graphics card is probably not able to run FlightGear 1.9 and higher. Another graphics card, or an older FlightGear version will likely "fix" the problem.

===Error: bind() failed in make_server_socket()===
When using [[Howto: Multiplayer|multiplayer]] or socket input, this usually means you specified an invalid ip address or the port is in use. Note: for multiplayer, you don't need to use the ''--multiplay=in,...'' option at all, FlightGear (since version 1.0) figures out the proper setting automatically. Only use when you know what you are doing.

===Error Building Technique: findAttr: could not find attribute bool===
Make sure that your data and source (or binary) match. They must be from the same date, to provide the best performance.

===Error: connect() failed in make_client_socket() SG_IO_OUT socket creation failed===
Your computer is not connected with the internet.

===Error: RenderTexture requires the following unsupported OpenGL extensions...===
Your graphics card doesn't support some graphics feature that FG requires. Update your drivers, change the BPP value and/or try disabling some of the visual goodies like [[3D Clouds]].

===Failed to find .... in apt.dat.gz===
You need to edit ATC/default.tower and ATC/default.atis. You can open these files with any text editor. Either remove or fix the entries containing your airports ICAO code (like KSFO).

===Failed to locate aircraft carrier = ...===
FlightGear is unable to find a [[Aircraft carrier|carrier]] under the set name. Check your commandline (<tt>--carrier=...</tt>) or the [[FlightGear Launch Control#Page Three - Airport Selection|airport page]] of the launcher.

'''Hint:''' Make sure your park position and carrier name is correct. See the [[Howto: Carrier|wiki's carrier page]] for details.

===Failed to open file ...===
Check if the file exists on your system. If the missing file is a scenery object; be sure you have the latest [http://scenemodels.flightgear.org/download/SharedModels.tgz Shared Models] from the [[FlightGear Scenery Database]].

===Fatal error: mismatched tag ...===
In some .xml file, an opening tag (like <tt><sim></tt>) does not match its closing tag (like <tt></sim></tt>). This error is hard to track down, best method is to comment (place code between <nowiki></nowiki>) most of the aircraft. Then uncomment code one by one, until the error appears again.

'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a tag is mis-matched and which tag is mis-matched. You'll probably know there's a problem if IE displays an error message.

===Fatal error: name must begin with alpha or '_'===
This error comes up when a property should be formed of which the name does not start with a letter of the alphabet or _. If this error only happens with certain planes, contact their authors.

===Fatal error: unclosed token===
A token (<nowiki></nowiki>) has been started, but not closes. Add <nowiki>--></nowiki> at the correct line.

'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a comment/token is not closed.

===FGMultiplayMgr::MP_ProcessData: No such file or directory===
This is telling you that there's someone online on the multiplayerserver, using a plane that you do not have installed on your own system. In order to remove the error (and see the other plane) you have to install the plane that the other pilot is using.

===FGMultiplayMgr - No receiver port, Multiplayermode disabled===
FlightGear [[Howto: Multiplayer|multiplayer]] has not been set.

===FGPropertyManager::GetNode() No node found for ... In component: ... unknown property ... referenced. Aborting===
FlightGear found a reference in the [[FDM]] to a non-existing property.

===FGPropertyManager::GetNode() No node found for ... The property ... is undefined.===
FlightGear found a reference in the [[FDM]] to a non-existing property. Keep in mind that JSBSim reads the FDM from top to bottom. Properties should always be created before they are needed somewhere.

===Fgtzfile_read(): : Invalid argument Fatal error: Timezone reading failed===
This one is caused by wrong line ending in a timezone file. Solution might be to download the Timezone/time.tab file manually from [http://gitorious.org/fg/fgdata/blobs/raw/master/Timezone/zone.tab Gitorious] (Right mouseclick > Save target as) and overwrite the file in <tt>[[$FG_ROOT]]/Timezone/time.tab</tt> with it.

===Found unexpected subsystem: system exiting. JSBSim failed to load aircraft and/or engine model===
You are probably trying to run an aircraft on a out-of-date version of FlightGear. The planes on the official download page are intended to be used with the latest version of FlightGear. Usage on any older systems may not work.

===freeglut (fgfs): Unable to create direct context rendering for window 'FlightGear' This may hurt performance===
This reports that you do not have proper hardware accelerated 3D (direct rendering) configured.

===Gate ... doesn't seem to have routes associated with it===
A startup location in the [[Interactive Traffic#Ground networks|groundnetwork]] is not (properly) connected to a taxi route. Contact the airport author, or import the network to [[TaxiDraw]] and run the Verify network command to find the corrupted gate.

===glLinkProgram "" Failed===
Update your drivers; they have to support atleast OpenGL 2.0 for FlightGear 2.0 and later.

===loading scenario '...'===
This is not an error. It shows that an [[AI Systems#AI Models|AI scenario]] is loaded.

===Model not found: ...===
This one tells you that FlightGear was unable to find a certain file. The nice thing is that it also tells you excactly what file.

# Check if the file really does not exist at your computer.
# Try to locate the file in which the missing file is referenced. This is likely to be <tt>-set.xml</tt> in the root directory of the loaded [[aircraft]]. Between the <model> tags, the base model file is referenced. This file references to all other models that are displayed with the aircraft.
# Contact the aircraft author with a detailed bug-report, in which you state the excact location of the missing file and (if you found it) the file in which it is referenced.

===Nasal runtime error: nil used in numeric context===
This error is [[Nasal]] triggered by a Nasal file (the console should show what file (and line) and from where it was referenced). The Nasal script tried to do something with a [[Property Tree|property]] with an empty value. A solution is to fill the property before the Nasal is loaded. This can be done by setting the property in an [[aircraft]]'s <tt>-set.xml</tt> file or by adding a [[Nasal scripting language#Listeners and Signals|listener]] to the script.

[[Howto: Contact the developers|Contact the developers]] if this error is shown for a <tt>[[$FG_ROOT]]/Nasal/</tt> script.

===Near camera not rendering===
[[Image:Near_camera_off.png|500px]]

If you screen looks like the image above; make sure you have at least [[OSG]] version 2.7.6.

===No render bin name specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===No render bin number specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===... not a valid win32 application===
This Windows error could have various reasons to pop up. Usually, the file that is causing troubles is mentioned. Re-installing this file might solve the problem.

===OBJECT_SIGN: unsupported glyph `.'===
Check the OBJECT_SIGN lines in the .stg file of the tile that was loaded when this error showed up.

===OpenAL error <AL_INVALID_VALUE>: bind source <alGenSources> Failed to generate audio source.===
This error is probably displayed because of some misdirected audio settings in the [[aircraft]]s setup. Check the -sound.xml file of the aircraft and see if all files refered to really exist. If not, try to contact the author of the plane, so he can fix the problem in the [[FlightGear CVS|CVS]] version or solve the problem yourself and let someone commit the patch.

===OpenAL error (AL_INVALID_VALUE): constructor (alBufferData) Fatal error: Failed to buffer data.===
Disabling sound is a temporarily solution for this problem.

===osgDB ac3d reader: could not find texture...===
See [[#Failed to open file ...|Failed to open file ...]]

===osgDB ac3d reader: detected surface with less than 3 vertices!===
In one of the loaded models a non-existing surface is found. This can be a single line (sometimes used to simulate thin wires) or a fault in the model.

===Program's vertex attrib binding ..., usrAttr...===
Tells you that an effect binded certain attributes to a [[Shaders|shader]].

===QNAN===
(Q)NAN stands for (Quiet) Not A Number, produced by 0/0 or other floating point break downs. There can be various causes for this:
* Using a "flap start" value of 0 in the [[YASim]] [[FDM]]. Use some small value like 0.001 instead.

===Scaling image...===
This means a texture, whether in the scenery on your aircraft or anyone elses (when multiplayer is enabled), is not sized to powers of two. All textures in FlightGear have to be sized to power of two (eg. 16*16, 32*64, 32*1024). As of version 1.9 textures are resized automaticly, but it does slow your computer down, so it's better to resize the noted textures.

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

===The system cannot find the file specified===
If you are running Windows Vista; start by looking in <tt>C:\Users\Owner\AppData\Local\VirtualStore</tt> and seeing if you have a folder called FlightGear in there. If you do, cut-and-paste (merge) that one with <tt>C:\Program Files\Flightgear</tt> and try to launch FlightGear again.

'''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible.

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

===Traffic manager could not find airport===
There is either an airport missing from apt.dat, or there is a wrong ICAO code in a [[Interactive Traffic#Building Traffic Files|traffic file]]. An airport missing from apt.dat could be due to a recent opening.

===Unable to choose requested pixel format===
Error should be solved as of version 1.9. If not, try changing your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] and/or resolution.

===Unable to find airport details for .... in FGTower::Init()===
This error can be surpressed by disabling [[Interactive Traffic|AI Traffic]], via the AI/ATC [[menu]].

The error appears when an airport in <tt>[[$FG_ROOT]]/Airports/apt.dat.gz</tt> cannot be found in <tt>[[$FG_ROOT]]/ATC/default.tower</tt> and <tt>[[$FG_ROOT]]/ATC/default.atis</tt>. Renaming the airports in the apt.dat.gz file ór in both default ATC files will fix the problem.

===Unable to open aircraft directory===
The [[aircraft]] that you are trying to run most likely relies on another aircraft, which you did not install (yet). The error shows what aircraft, so go download that one!
=== Unexpected tag '...' found in YASim aircraft description===
FlightGear found a non-existing tag in the [[FDM]] of the aircraft you are trying to launch. If you have not changed the original aircraft, contact the aircraft author. Else, check the FDM througly for mistakes.

Also, make sure you didn't force a FDM to be loaded.
* '''Commandline:''' <tt>--fdm=...</tt> should be left out.
* '''[[FGRun]]:''' <tt>Advanced > Flight Model</tt> should be set to jsb (which will leave the whole command out of the commandline, so you can use this setting with any FDM).

=== Unknown ... aircraft: ... defaulting to C172 ===
FlightGear is unable to load the forced [[FDM]] (set through <tt>--fdm=...</tt> or via <tt>Advanced > Flight Model</tt> in [[FGRun]]) for this aircraft. FlightGear automatically picks the right FDM for each aircraft, so there is no need to set it manually, unless you know what you are doing. In the Flight Model dialog of FGRun, set the FDM to <tt>jsb</tt>; that is the "auto setting".

===Unknown exception to the main loop. Aborting... Possible cause: No such file or directory===
This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear_Launch_Control#Debugging|log level]] to debug and repeating excactly what you did when the error came up, might provide some more information on what FlightGear was doing when the error occurred.
* Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work.
* Changing the resolution to a smaller one might work as well.

===WARNING: Couldn't convert texture...===
You are trying to run an aircraft not compatible with your FlightGear version. Most of the time, this error appears when you fly an aircraft, textured with .png files on versions older than 1.9. Convert the textures manually to .rgb or upgrade your FlightGear version.

===Warning: Could not find plugin to read objects from file ...===
A library is missing from your computer. Therefore, certain fileformats cannot be read. Try to reinstall/update [[OSG]], as the libraries used by FlightGear should be part of the standard package.

===Warning: Picked up TriangleIntersect===
Reduce your [[FlightGear Launch Control#Debugging|Log Level]] to alert. Or [[Showstoppers|send the fgfs output to /dev/null (unix systems) or 2>nul (Windows)]]. The errors might still be shown, but do not affect the sim anymore.

===Warning: TangentSpaceGenerator: unknown primitive mode 9===
This is an [[OSG]] error, showing up when an effect needs tangent vectors, but polygons are not support. The error itself can be ignored, altough some [[shaders]] may look wrong. Shader developers should try to minimise the use of polygons and use triangles and quads instead.

===YASim SOLUTION FAILURE: Solution failed to converge after 10000 iterations===
Some control in the [[YASim]] [[FDM]] is too weak, according to YASim, to control the aircraft. An effectiveness tag will be required in the FDM to solve this error.

===YASim SOLUTION FAILURE: Zero length fuselage===
There is a problem in the [[FDM]]. A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.

===FGMultiplayerMgr::Open - Failed to bind receive socket===

This means FlightGear was unable to open the listening network socket required by the --multiplay=in option. Frequently this option can be omitted and FlightGear will figure out the necessary parameters automatically.
Common reasons are:
* Address given in the option does not resolve to one of the IP addresses of the local machine. This parameter should only be required if you want to fine-tune the network behavior. Omitting it directs FlightGear to listen on all local interfaces automatically. Example:
--multiplay=in,10,,5001
Notice that you still need the comma.
* The UDP port given in the option (or the default port 5000 if no option given) is already in use. Verify nothing is using the port.

==Errors without known solutions==
Please take a look at the upcoming errors and see if you know a solution to get rid of them. Your additions are greatly appreciated!

===AL Error (fx): Invalid Value at pitch and gain===

===AL Error (sound manager): Invalid Operation at update===

===AL Error (sound manager): Invalid Value at buffer add data No such buffer!===

===Failed to execute command nasal===

===Failed to tie property ... to object methods===
A JSBSim error.

===FGMultiplayMgr::MP_ProcessData - message from ... has invalid length!===

===FGMultiplayMgr::MP_ProcessData: Result too large===

===GPS: malformed route, index=1===

===Mesa 7.3 implementation error: bad texture level in r300UploadSubImage===
http://www.flightgear.org/forums/viewtopic.php?f=2&t=6706&start=0&st=0&sk=t&sd=a

===Nasal runtime error: stack overflow===

===No image file for texture, using white===
A [[Shaders|shader]] error, possibly you (or the developer) have/has not specified a texture for a surface while modeling the aircraft model in AC3D, Blender, Wings...

===No path in /sim/sound/path===

You (or the developer) have/has not specified a proper sound file in the aircraft's -set.xml file.

===OBJECT_SIGN: unexpected } in sign contents===

===OpenAL error (AL_ILLEGAL_COMMAND): set_source_pos===

Has something to do with OpenAL not understanding where the sound comes from.

===OpenAL error (AL_ILLEGAL_COMMAND): set_volume===

Has something to do with OpenAL not understanding the sound volume.

===PT_vs_hpt: ran out of layers===
This is issued from the atmosphere implementation in FlightGear's environment system. A comment in the code says: "''should never get here''". Please provide input when this happens: excessive altitudes? Negative altitudes?

===Warning: detected OpenGL error 'invalid value' after RenderBin::draw(,)===
This warning is generated from OSG. Set your environment variable
OSG_NOTIFY_LEVEL=FATAL

===Warning: GraphicsWindowWin32::grabFocus() - Failed grabbing the focus===

It seems that this happens when you have another window open and you are "focusing" (the window is active) on it. FlightGear will try to grab itself infront of the other window.

===WARNING: PUI: Too many live puInterfaces open at once!===
Appears when printing large outputs (very) frequently on the screen.

===Warning: State::drawQuads(0, 154400) too large handle in remapping to ushort glDrawElements===

[[Category:Howto|Get rid of common errors]]

[[fr:Howto: Débarrassez-vous des erreurs les plus fréquentes]]

Howto:Understand console output

2010-11-28T22:29:17Z

Airbird1: /* Failed to locate aircraft carrier = ... */ Added Hint

This document lists '''[[FlightGear]] errors''', how to get rid of them and other '''console output'''. If FlightGear quits but does not give you any error, try increasing the [[FlightGear Launch Control#Debugging|Log Level]].

Errors can appear in various locations, but the most common one is the console (a black window), which pops up when you run fgfs.exe.

==Errors with known solutions==
===Airports/.... ... Done===
This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG_SCENERY]]/Airports</tt> directory.

===Base package check failed ... Found version [none] at: ... Please upgrade to version:===
* FlightGear was unable to find the [[$FG_ROOT]] directory. Set it using the <tt>--fg-root=</tt> commandline option.
* When using [[CVS]] with binaries, the data must match the binary. You cannot use data from a different date than the binary's release date.

===condition: comparison without property[1] or value===
A condition (like <tt><less-than></tt> or <tt><equals></tt>) exists, without either:
* a property to check
* a value to check the property against

===Could not find at least one of the following objects for animation:===
This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. If you are not the aircraft's author you can safely ignore such warnings.

===creating 3D noise texture... DONE===
Tells you that a new noise texture is created. It is not an error and can be ignored.

===Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified====
Try changing the [[FlightGear Launch Control#Page Four - Options and Run|BPP]] value of your FlightGear setup. If that does not work, your graphics card is probably not able to run FlightGear 1.9 and higher. Another graphics card, or an older FlightGear version will likely "fix" the problem.

===Error: bind() failed in make_server_socket()===
When using [[Howto: Multiplayer|multiplayer]] or socket input, this usually means you specified an invalid ip address or the port is in use. Note: for multiplayer, you don't need to use the ''--multiplay=in,...'' option at all, FlightGear (since version 1.0) figures out the proper setting automatically. Only use when you know what you are doing.

===Error Building Technique: findAttr: could not find attribute bool===
Make sure that your data and source (or binary) match. They must be from the same date, to provide the best performance.

===Error: connect() failed in make_client_socket() SG_IO_OUT socket creation failed===
Your computer is not connected with the internet.

===Error: RenderTexture requires the following unsupported OpenGL extensions...===
Your graphics card doesn't support some graphics feature that FG requires. Update your drivers, change the BPP value and/or try disabling some of the visual goodies like [[3D Clouds]].

===Failed to find .... in apt.dat.gz===
You need to edit ATC/default.tower and ATC/default.atis. You can open these files with any text editor. Either remove or fix the entries containing your airports ICAO code (like KSFO).

===Failed to locate aircraft carrier = ...===
FlightGear is unable to find a [[Aircraft carrier|carrier]] under the set name. Check your commandline (<tt>--carrier=...</tt>) or the [[FlightGear Launch Control#Page Three - Airport Selection|airport page]] of the launcher.

'''Hint:''' Make sure your park position and carrier name is correct. See the [[Howto: Carrier|wiki's carrier page]] for details.

===Failed to open file ...===
Check if the file exists on your system. If the missing file is a scenery object; be sure you have the latest [http://scenemodels.flightgear.org/download/SharedModels.tgz Shared Models] from the [[FlightGear Scenery Database]].

===Fatal error: mismatched tag ...===
In some .xml file, an opening tag (like <tt><sim></tt>) does not match its closing tag (like <tt></sim></tt>). This error is hard to track down, best method is to comment (place code between <nowiki></nowiki>) most of the aircraft. Then uncomment code one by one, until the error appears again.

'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a tag is mis-matched and which tag is mis-matched. You'll probably know there's a problem if IE displays an error message.

===Fatal error: name must begin with alpha or '_'===
This error comes up when a property should be formed of which the name does not start with a letter of the alphabet or _. If this error only happens with certain planes, contact their authors.

===Fatal error: unclosed token===
A token (<nowiki></nowiki>) has been started, but not closes. Add <nowiki>--></nowiki> at the correct line.

===FGMultiplayMgr::MP_ProcessData: No such file or directory===
This is telling you that there's someone online on the multiplayerserver, using a plane that you do not have installed on your own system. In order to remove the error (and see the other plane) you have to install the plane that the other pilot is using.

===FGMultiplayMgr - No receiver port, Multiplayermode disabled===
FlightGear [[Howto: Multiplayer|multiplayer]] has not been set.

===FGPropertyManager::GetNode() No node found for ... In component: ... unknown property ... referenced. Aborting===
FlightGear found a reference in the [[FDM]] to a non-existing property.

===FGPropertyManager::GetNode() No node found for ... The property ... is undefined.===
FlightGear found a reference in the [[FDM]] to a non-existing property. Keep in mind that JSBSim reads the FDM from top to bottom. Properties should always be created before they are needed somewhere.

===Fgtzfile_read(): : Invalid argument Fatal error: Timezone reading failed===
This one is caused by wrong line ending in a timezone file. Solution might be to download the Timezone/time.tab file manually from [http://gitorious.org/fg/fgdata/blobs/raw/master/Timezone/zone.tab Gitorious] (Right mouseclick > Save target as) and overwrite the file in <tt>[[$FG_ROOT]]/Timezone/time.tab</tt> with it.

===Found unexpected subsystem: system exiting. JSBSim failed to load aircraft and/or engine model===
You are probably trying to run an aircraft on a out-of-date version of FlightGear. The planes on the official download page are intended to be used with the latest version of FlightGear. Usage on any older systems may not work.

===freeglut (fgfs): Unable to create direct context rendering for window 'FlightGear' This may hurt performance===
This reports that you do not have proper hardware accelerated 3D (direct rendering) configured.

===Gate ... doesn't seem to have routes associated with it===
A startup location in the [[Interactive Traffic#Ground networks|groundnetwork]] is not (properly) connected to a taxi route. Contact the airport author, or import the network to [[TaxiDraw]] and run the Verify network command to find the corrupted gate.

===glLinkProgram "" Failed===
Update your drivers; they have to support atleast OpenGL 2.0 for FlightGear 2.0 and later.

===loading scenario '...'===
This is not an error. It shows that an [[AI Systems#AI Models|AI scenario]] is loaded.

===Model not found: ...===
This one tells you that FlightGear was unable to find a certain file. The nice thing is that it also tells you excactly what file.

# Check if the file really does not exist at your computer.
# Try to locate the file in which the missing file is referenced. This is likely to be <tt>-set.xml</tt> in the root directory of the loaded [[aircraft]]. Between the <model> tags, the base model file is referenced. This file references to all other models that are displayed with the aircraft.
# Contact the aircraft author with a detailed bug-report, in which you state the excact location of the missing file and (if you found it) the file in which it is referenced.

===Nasal runtime error: nil used in numeric context===
This error is [[Nasal]] triggered by a Nasal file (the console should show what file (and line) and from where it was referenced). The Nasal script tried to do something with a [[Property Tree|property]] with an empty value. A solution is to fill the property before the Nasal is loaded. This can be done by setting the property in an [[aircraft]]'s <tt>-set.xml</tt> file or by adding a [[Nasal scripting language#Listeners and Signals|listener]] to the script.

[[Howto: Contact the developers|Contact the developers]] if this error is shown for a <tt>[[$FG_ROOT]]/Nasal/</tt> script.

===Near camera not rendering===
[[Image:Near_camera_off.png|500px]]

If you screen looks like the image above; make sure you have at least [[OSG]] version 2.7.6.

===No render bin name specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===No render bin number specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===... not a valid win32 application===
This Windows error could have various reasons to pop up. Usually, the file that is causing troubles is mentioned. Re-installing this file might solve the problem.

===OBJECT_SIGN: unsupported glyph `.'===
Check the OBJECT_SIGN lines in the .stg file of the tile that was loaded when this error showed up.

===OpenAL error <AL_INVALID_VALUE>: bind source <alGenSources> Failed to generate audio source.===
This error is probably displayed because of some misdirected audio settings in the [[aircraft]]s setup. Check the -sound.xml file of the aircraft and see if all files refered to really exist. If not, try to contact the author of the plane, so he can fix the problem in the [[FlightGear CVS|CVS]] version or solve the problem yourself and let someone commit the patch.

===OpenAL error (AL_INVALID_VALUE): constructor (alBufferData) Fatal error: Failed to buffer data.===
Disabling sound is a temporarily solution for this problem.

===osgDB ac3d reader: could not find texture...===
See [[#Failed to open file ...|Failed to open file ...]]

===osgDB ac3d reader: detected surface with less than 3 vertices!===
In one of the loaded models a non-existing surface is found. This can be a single line (sometimes used to simulate thin wires) or a fault in the model.

===Program's vertex attrib binding ..., usrAttr...===
Tells you that an effect binded certain attributes to a [[Shaders|shader]].

===QNAN===
(Q)NAN stands for (Quiet) Not A Number, produced by 0/0 or other floating point break downs. There can be various causes for this:
* Using a "flap start" value of 0 in the [[YASim]] [[FDM]]. Use some small value like 0.001 instead.

===Scaling image...===
This means a texture, whether in the scenery on your aircraft or anyone elses (when multiplayer is enabled), is not sized to powers of two. All textures in FlightGear have to be sized to power of two (eg. 16*16, 32*64, 32*1024). As of version 1.9 textures are resized automaticly, but it does slow your computer down, so it's better to resize the noted textures.

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

===The system cannot find the file specified===
If you are running Windows Vista; start by looking in <tt>C:\Users\Owner\AppData\Local\VirtualStore</tt> and seeing if you have a folder called FlightGear in there. If you do, cut-and-paste (merge) that one with <tt>C:\Program Files\Flightgear</tt> and try to launch FlightGear again.

'''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible.

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

===Traffic manager could not find airport===
There is either an airport missing from apt.dat, or there is a wrong ICAO code in a [[Interactive Traffic#Building Traffic Files|traffic file]]. An airport missing from apt.dat could be due to a recent opening.

===Unable to choose requested pixel format===
Error should be solved as of version 1.9. If not, try changing your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] and/or resolution.

===Unable to find airport details for .... in FGTower::Init()===
This error can be surpressed by disabling [[Interactive Traffic|AI Traffic]], via the AI/ATC [[menu]].

The error appears when an airport in <tt>[[$FG_ROOT]]/Airports/apt.dat.gz</tt> cannot be found in <tt>[[$FG_ROOT]]/ATC/default.tower</tt> and <tt>[[$FG_ROOT]]/ATC/default.atis</tt>. Renaming the airports in the apt.dat.gz file ór in both default ATC files will fix the problem.

===Unable to open aircraft directory===
The [[aircraft]] that you are trying to run most likely relies on another aircraft, which you did not install (yet). The error shows what aircraft, so go download that one!
=== Unexpected tag '...' found in YASim aircraft description===
FlightGear found a non-existing tag in the [[FDM]] of the aircraft you are trying to launch. If you have not changed the original aircraft, contact the aircraft author. Else, check the FDM througly for mistakes.

Also, make sure you didn't force a FDM to be loaded.
* '''Commandline:''' <tt>--fdm=...</tt> should be left out.
* '''[[FGRun]]:''' <tt>Advanced > Flight Model</tt> should be set to jsb (which will leave the whole command out of the commandline, so you can use this setting with any FDM).

=== Unknown ... aircraft: ... defaulting to C172 ===
FlightGear is unable to load the forced [[FDM]] (set through <tt>--fdm=...</tt> or via <tt>Advanced > Flight Model</tt> in [[FGRun]]) for this aircraft. FlightGear automatically picks the right FDM for each aircraft, so there is no need to set it manually, unless you know what you are doing. In the Flight Model dialog of FGRun, set the FDM to <tt>jsb</tt>; that is the "auto setting".

===Unknown exception to the main loop. Aborting... Possible cause: No such file or directory===
This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear_Launch_Control#Debugging|log level]] to debug and repeating excactly what you did when the error came up, might provide some more information on what FlightGear was doing when the error occurred.
* Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work.
* Changing the resolution to a smaller one might work as well.

===WARNING: Couldn't convert texture...===
You are trying to run an aircraft not compatible with your FlightGear version. Most of the time, this error appears when you fly an aircraft, textured with .png files on versions older than 1.9. Convert the textures manually to .rgb or upgrade your FlightGear version.

===Warning: Could not find plugin to read objects from file ...===
A library is missing from your computer. Therefore, certain fileformats cannot be read. Try to reinstall/update [[OSG]], as the libraries used by FlightGear should be part of the standard package.

===Warning: Picked up TriangleIntersect===
Reduce your [[FlightGear Launch Control#Debugging|Log Level]] to alert. Or [[Showstoppers|send the fgfs output to /dev/null (unix systems) or 2>nul (Windows)]]. The errors might still be shown, but do not affect the sim anymore.

===Warning: TangentSpaceGenerator: unknown primitive mode 9===
This is an [[OSG]] error, showing up when an effect needs tangent vectors, but polygons are not support. The error itself can be ignored, altough some [[shaders]] may look wrong. Shader developers should try to minimise the use of polygons and use triangles and quads instead.

===YASim SOLUTION FAILURE: Solution failed to converge after 10000 iterations===
Some control in the [[YASim]] [[FDM]] is too weak, according to YASim, to control the aircraft. An effectiveness tag will be required in the FDM to solve this error.

===YASim SOLUTION FAILURE: Zero length fuselage===
There is a problem in the [[FDM]]. A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.

===FGMultiplayerMgr::Open - Failed to bind receive socket===

This means FlightGear was unable to open the listening network socket required by the --multiplay=in option. Frequently this option can be omitted and FlightGear will figure out the necessary parameters automatically.
Common reasons are:
* Address given in the option does not resolve to one of the IP addresses of the local machine. This parameter should only be required if you want to fine-tune the network behavior. Omitting it directs FlightGear to listen on all local interfaces automatically. Example:
--multiplay=in,10,,5001
Notice that you still need the comma.
* The UDP port given in the option (or the default port 5000 if no option given) is already in use. Verify nothing is using the port.

==Errors without known solutions==
Please take a look at the upcoming errors and see if you know a solution to get rid of them. Your additions are greatly appreciated!

===AL Error (fx): Invalid Value at pitch and gain===

===AL Error (sound manager): Invalid Operation at update===

===AL Error (sound manager): Invalid Value at buffer add data No such buffer!===

===Failed to execute command nasal===

===Failed to tie property ... to object methods===
A JSBSim error.

===FGMultiplayMgr::MP_ProcessData - message from ... has invalid length!===

===FGMultiplayMgr::MP_ProcessData: Result too large===

===GPS: malformed route, index=1===

===Mesa 7.3 implementation error: bad texture level in r300UploadSubImage===
http://www.flightgear.org/forums/viewtopic.php?f=2&t=6706&start=0&st=0&sk=t&sd=a

===Nasal runtime error: stack overflow===

===No image file for texture, using white===
A [[Shaders|shader]] error, possibly you (or the developer) have/has not specified a texture for a surface while modeling the aircraft model in AC3D, Blender, Wings...

===No path in /sim/sound/path===

You (or the developer) have/has not specified a proper sound file in the aircraft's -set.xml file.

===OBJECT_SIGN: unexpected } in sign contents===

===OpenAL error (AL_ILLEGAL_COMMAND): set_source_pos===

Has something to do with OpenAL not understanding where the sound comes from.

===OpenAL error (AL_ILLEGAL_COMMAND): set_volume===

Has something to do with OpenAL not understanding the sound volume.

===PT_vs_hpt: ran out of layers===
This is issued from the atmosphere implementation in FlightGear's environment system. A comment in the code says: "''should never get here''". Please provide input when this happens: excessive altitudes? Negative altitudes?

===Warning: detected OpenGL error 'invalid value' after RenderBin::draw(,)===
This warning is generated from OSG. Set your environment variable
OSG_NOTIFY_LEVEL=FATAL

===Warning: GraphicsWindowWin32::grabFocus() - Failed grabbing the focus===

It seems that this happens when you have another window open and you are "focusing" (the window is active) on it. FlightGear will try to grab itself infront of the other window.

===WARNING: PUI: Too many live puInterfaces open at once!===
Appears when printing large outputs (very) frequently on the screen.

===Warning: State::drawQuads(0, 154400) too large handle in remapping to ushort glDrawElements===

[[Category:Howto|Get rid of common errors]]

[[fr:Howto: Débarrassez-vous des erreurs les plus fréquentes]]

Howto:Understand console output

2010-11-28T22:25:12Z

Airbird1: /* Fatal error: mismatched tag ... */ Added "Hint for developers"

This document lists '''[[FlightGear]] errors''', how to get rid of them and other '''console output'''. If FlightGear quits but does not give you any error, try increasing the [[FlightGear Launch Control#Debugging|Log Level]].

Errors can appear in various locations, but the most common one is the console (a black window), which pops up when you run fgfs.exe.

==Errors with known solutions==
===Airports/.... ... Done===
This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG_SCENERY]]/Airports</tt> directory.

===Base package check failed ... Found version [none] at: ... Please upgrade to version:===
* FlightGear was unable to find the [[$FG_ROOT]] directory. Set it using the <tt>--fg-root=</tt> commandline option.
* When using [[CVS]] with binaries, the data must match the binary. You cannot use data from a different date than the binary's release date.

===condition: comparison without property[1] or value===
A condition (like <tt><less-than></tt> or <tt><equals></tt>) exists, without either:
* a property to check
* a value to check the property against

===Could not find at least one of the following objects for animation:===
This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. If you are not the aircraft's author you can safely ignore such warnings.

===creating 3D noise texture... DONE===
Tells you that a new noise texture is created. It is not an error and can be ignored.

===Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified====
Try changing the [[FlightGear Launch Control#Page Four - Options and Run|BPP]] value of your FlightGear setup. If that does not work, your graphics card is probably not able to run FlightGear 1.9 and higher. Another graphics card, or an older FlightGear version will likely "fix" the problem.

===Error: bind() failed in make_server_socket()===
When using [[Howto: Multiplayer|multiplayer]] or socket input, this usually means you specified an invalid ip address or the port is in use. Note: for multiplayer, you don't need to use the ''--multiplay=in,...'' option at all, FlightGear (since version 1.0) figures out the proper setting automatically. Only use when you know what you are doing.

===Error Building Technique: findAttr: could not find attribute bool===
Make sure that your data and source (or binary) match. They must be from the same date, to provide the best performance.

===Error: connect() failed in make_client_socket() SG_IO_OUT socket creation failed===
Your computer is not connected with the internet.

===Error: RenderTexture requires the following unsupported OpenGL extensions...===
Your graphics card doesn't support some graphics feature that FG requires. Update your drivers, change the BPP value and/or try disabling some of the visual goodies like [[3D Clouds]].

===Failed to find .... in apt.dat.gz===
You need to edit ATC/default.tower and ATC/default.atis. You can open these files with any text editor. Either remove or fix the entries containing your airports ICAO code (like KSFO).

===Failed to locate aircraft carrier = ...===
FlightGear is unable to find a [[Aircraft carrier|carrier]] under the set name. Check your commandline (<tt>--carrier=...</tt>) or the [[FlightGear Launch Control#Page Three - Airport Selection|airport page]] of the launcher.

===Failed to open file ...===
Check if the file exists on your system. If the missing file is a scenery object; be sure you have the latest [http://scenemodels.flightgear.org/download/SharedModels.tgz Shared Models] from the [[FlightGear Scenery Database]].

===Fatal error: mismatched tag ...===
In some .xml file, an opening tag (like <tt><sim></tt>) does not match its closing tag (like <tt></sim></tt>). This error is hard to track down, best method is to comment (place code between <nowiki></nowiki>) most of the aircraft. Then uncomment code one by one, until the error appears again.

'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a tag is mis-matched and which tag is mis-matched. You'll probably know there's a problem if IE displays an error message.

===Fatal error: name must begin with alpha or '_'===
This error comes up when a property should be formed of which the name does not start with a letter of the alphabet or _. If this error only happens with certain planes, contact their authors.

===Fatal error: unclosed token===
A token (<nowiki></nowiki>) has been started, but not closes. Add <nowiki>--></nowiki> at the correct line.

===FGMultiplayMgr::MP_ProcessData: No such file or directory===
This is telling you that there's someone online on the multiplayerserver, using a plane that you do not have installed on your own system. In order to remove the error (and see the other plane) you have to install the plane that the other pilot is using.

===FGMultiplayMgr - No receiver port, Multiplayermode disabled===
FlightGear [[Howto: Multiplayer|multiplayer]] has not been set.

===FGPropertyManager::GetNode() No node found for ... In component: ... unknown property ... referenced. Aborting===
FlightGear found a reference in the [[FDM]] to a non-existing property.

===FGPropertyManager::GetNode() No node found for ... The property ... is undefined.===
FlightGear found a reference in the [[FDM]] to a non-existing property. Keep in mind that JSBSim reads the FDM from top to bottom. Properties should always be created before they are needed somewhere.

===Fgtzfile_read(): : Invalid argument Fatal error: Timezone reading failed===
This one is caused by wrong line ending in a timezone file. Solution might be to download the Timezone/time.tab file manually from [http://gitorious.org/fg/fgdata/blobs/raw/master/Timezone/zone.tab Gitorious] (Right mouseclick > Save target as) and overwrite the file in <tt>[[$FG_ROOT]]/Timezone/time.tab</tt> with it.

===Found unexpected subsystem: system exiting. JSBSim failed to load aircraft and/or engine model===
You are probably trying to run an aircraft on a out-of-date version of FlightGear. The planes on the official download page are intended to be used with the latest version of FlightGear. Usage on any older systems may not work.

===freeglut (fgfs): Unable to create direct context rendering for window 'FlightGear' This may hurt performance===
This reports that you do not have proper hardware accelerated 3D (direct rendering) configured.

===Gate ... doesn't seem to have routes associated with it===
A startup location in the [[Interactive Traffic#Ground networks|groundnetwork]] is not (properly) connected to a taxi route. Contact the airport author, or import the network to [[TaxiDraw]] and run the Verify network command to find the corrupted gate.

===glLinkProgram "" Failed===
Update your drivers; they have to support atleast OpenGL 2.0 for FlightGear 2.0 and later.

===loading scenario '...'===
This is not an error. It shows that an [[AI Systems#AI Models|AI scenario]] is loaded.

===Model not found: ...===
This one tells you that FlightGear was unable to find a certain file. The nice thing is that it also tells you excactly what file.

# Check if the file really does not exist at your computer.
# Try to locate the file in which the missing file is referenced. This is likely to be <tt>-set.xml</tt> in the root directory of the loaded [[aircraft]]. Between the <model> tags, the base model file is referenced. This file references to all other models that are displayed with the aircraft.
# Contact the aircraft author with a detailed bug-report, in which you state the excact location of the missing file and (if you found it) the file in which it is referenced.

===Nasal runtime error: nil used in numeric context===
This error is [[Nasal]] triggered by a Nasal file (the console should show what file (and line) and from where it was referenced). The Nasal script tried to do something with a [[Property Tree|property]] with an empty value. A solution is to fill the property before the Nasal is loaded. This can be done by setting the property in an [[aircraft]]'s <tt>-set.xml</tt> file or by adding a [[Nasal scripting language#Listeners and Signals|listener]] to the script.

[[Howto: Contact the developers|Contact the developers]] if this error is shown for a <tt>[[$FG_ROOT]]/Nasal/</tt> script.

===Near camera not rendering===
[[Image:Near_camera_off.png|500px]]

If you screen looks like the image above; make sure you have at least [[OSG]] version 2.7.6.

===No render bin name specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===No render bin number specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===... not a valid win32 application===
This Windows error could have various reasons to pop up. Usually, the file that is causing troubles is mentioned. Re-installing this file might solve the problem.

===OBJECT_SIGN: unsupported glyph `.'===
Check the OBJECT_SIGN lines in the .stg file of the tile that was loaded when this error showed up.

===OpenAL error <AL_INVALID_VALUE>: bind source <alGenSources> Failed to generate audio source.===
This error is probably displayed because of some misdirected audio settings in the [[aircraft]]s setup. Check the -sound.xml file of the aircraft and see if all files refered to really exist. If not, try to contact the author of the plane, so he can fix the problem in the [[FlightGear CVS|CVS]] version or solve the problem yourself and let someone commit the patch.

===OpenAL error (AL_INVALID_VALUE): constructor (alBufferData) Fatal error: Failed to buffer data.===
Disabling sound is a temporarily solution for this problem.

===osgDB ac3d reader: could not find texture...===
See [[#Failed to open file ...|Failed to open file ...]]

===osgDB ac3d reader: detected surface with less than 3 vertices!===
In one of the loaded models a non-existing surface is found. This can be a single line (sometimes used to simulate thin wires) or a fault in the model.

===Program's vertex attrib binding ..., usrAttr...===
Tells you that an effect binded certain attributes to a [[Shaders|shader]].

===QNAN===
(Q)NAN stands for (Quiet) Not A Number, produced by 0/0 or other floating point break downs. There can be various causes for this:
* Using a "flap start" value of 0 in the [[YASim]] [[FDM]]. Use some small value like 0.001 instead.

===Scaling image...===
This means a texture, whether in the scenery on your aircraft or anyone elses (when multiplayer is enabled), is not sized to powers of two. All textures in FlightGear have to be sized to power of two (eg. 16*16, 32*64, 32*1024). As of version 1.9 textures are resized automaticly, but it does slow your computer down, so it's better to resize the noted textures.

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

===The system cannot find the file specified===
If you are running Windows Vista; start by looking in <tt>C:\Users\Owner\AppData\Local\VirtualStore</tt> and seeing if you have a folder called FlightGear in there. If you do, cut-and-paste (merge) that one with <tt>C:\Program Files\Flightgear</tt> and try to launch FlightGear again.

'''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible.

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

===Traffic manager could not find airport===
There is either an airport missing from apt.dat, or there is a wrong ICAO code in a [[Interactive Traffic#Building Traffic Files|traffic file]]. An airport missing from apt.dat could be due to a recent opening.

===Unable to choose requested pixel format===
Error should be solved as of version 1.9. If not, try changing your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] and/or resolution.

===Unable to find airport details for .... in FGTower::Init()===
This error can be surpressed by disabling [[Interactive Traffic|AI Traffic]], via the AI/ATC [[menu]].

The error appears when an airport in <tt>[[$FG_ROOT]]/Airports/apt.dat.gz</tt> cannot be found in <tt>[[$FG_ROOT]]/ATC/default.tower</tt> and <tt>[[$FG_ROOT]]/ATC/default.atis</tt>. Renaming the airports in the apt.dat.gz file ór in both default ATC files will fix the problem.

===Unable to open aircraft directory===
The [[aircraft]] that you are trying to run most likely relies on another aircraft, which you did not install (yet). The error shows what aircraft, so go download that one!
=== Unexpected tag '...' found in YASim aircraft description===
FlightGear found a non-existing tag in the [[FDM]] of the aircraft you are trying to launch. If you have not changed the original aircraft, contact the aircraft author. Else, check the FDM througly for mistakes.

Also, make sure you didn't force a FDM to be loaded.
* '''Commandline:''' <tt>--fdm=...</tt> should be left out.
* '''[[FGRun]]:''' <tt>Advanced > Flight Model</tt> should be set to jsb (which will leave the whole command out of the commandline, so you can use this setting with any FDM).

=== Unknown ... aircraft: ... defaulting to C172 ===
FlightGear is unable to load the forced [[FDM]] (set through <tt>--fdm=...</tt> or via <tt>Advanced > Flight Model</tt> in [[FGRun]]) for this aircraft. FlightGear automatically picks the right FDM for each aircraft, so there is no need to set it manually, unless you know what you are doing. In the Flight Model dialog of FGRun, set the FDM to <tt>jsb</tt>; that is the "auto setting".

===Unknown exception to the main loop. Aborting... Possible cause: No such file or directory===
This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear_Launch_Control#Debugging|log level]] to debug and repeating excactly what you did when the error came up, might provide some more information on what FlightGear was doing when the error occurred.
* Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work.
* Changing the resolution to a smaller one might work as well.

===WARNING: Couldn't convert texture...===
You are trying to run an aircraft not compatible with your FlightGear version. Most of the time, this error appears when you fly an aircraft, textured with .png files on versions older than 1.9. Convert the textures manually to .rgb or upgrade your FlightGear version.

===Warning: Could not find plugin to read objects from file ...===
A library is missing from your computer. Therefore, certain fileformats cannot be read. Try to reinstall/update [[OSG]], as the libraries used by FlightGear should be part of the standard package.

===Warning: Picked up TriangleIntersect===
Reduce your [[FlightGear Launch Control#Debugging|Log Level]] to alert. Or [[Showstoppers|send the fgfs output to /dev/null (unix systems) or 2>nul (Windows)]]. The errors might still be shown, but do not affect the sim anymore.

===Warning: TangentSpaceGenerator: unknown primitive mode 9===
This is an [[OSG]] error, showing up when an effect needs tangent vectors, but polygons are not support. The error itself can be ignored, altough some [[shaders]] may look wrong. Shader developers should try to minimise the use of polygons and use triangles and quads instead.

===YASim SOLUTION FAILURE: Solution failed to converge after 10000 iterations===
Some control in the [[YASim]] [[FDM]] is too weak, according to YASim, to control the aircraft. An effectiveness tag will be required in the FDM to solve this error.

===YASim SOLUTION FAILURE: Zero length fuselage===
There is a problem in the [[FDM]]. A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.

===FGMultiplayerMgr::Open - Failed to bind receive socket===

This means FlightGear was unable to open the listening network socket required by the --multiplay=in option. Frequently this option can be omitted and FlightGear will figure out the necessary parameters automatically.
Common reasons are:
* Address given in the option does not resolve to one of the IP addresses of the local machine. This parameter should only be required if you want to fine-tune the network behavior. Omitting it directs FlightGear to listen on all local interfaces automatically. Example:
--multiplay=in,10,,5001
Notice that you still need the comma.
* The UDP port given in the option (or the default port 5000 if no option given) is already in use. Verify nothing is using the port.

==Errors without known solutions==
Please take a look at the upcoming errors and see if you know a solution to get rid of them. Your additions are greatly appreciated!

===AL Error (fx): Invalid Value at pitch and gain===

===AL Error (sound manager): Invalid Operation at update===

===AL Error (sound manager): Invalid Value at buffer add data No such buffer!===

===Failed to execute command nasal===

===Failed to tie property ... to object methods===
A JSBSim error.

===FGMultiplayMgr::MP_ProcessData - message from ... has invalid length!===

===FGMultiplayMgr::MP_ProcessData: Result too large===

===GPS: malformed route, index=1===

===Mesa 7.3 implementation error: bad texture level in r300UploadSubImage===
http://www.flightgear.org/forums/viewtopic.php?f=2&t=6706&start=0&st=0&sk=t&sd=a

===Nasal runtime error: stack overflow===

===No image file for texture, using white===
A [[Shaders|shader]] error, possibly you (or the developer) have/has not specified a texture for a surface while modeling the aircraft model in AC3D, Blender, Wings...

===No path in /sim/sound/path===

You (or the developer) have/has not specified a proper sound file in the aircraft's -set.xml file.

===OBJECT_SIGN: unexpected } in sign contents===

===OpenAL error (AL_ILLEGAL_COMMAND): set_source_pos===

Has something to do with OpenAL not understanding where the sound comes from.

===OpenAL error (AL_ILLEGAL_COMMAND): set_volume===

Has something to do with OpenAL not understanding the sound volume.

===PT_vs_hpt: ran out of layers===
This is issued from the atmosphere implementation in FlightGear's environment system. A comment in the code says: "''should never get here''". Please provide input when this happens: excessive altitudes? Negative altitudes?

===Warning: detected OpenGL error 'invalid value' after RenderBin::draw(,)===
This warning is generated from OSG. Set your environment variable
OSG_NOTIFY_LEVEL=FATAL

===Warning: GraphicsWindowWin32::grabFocus() - Failed grabbing the focus===

It seems that this happens when you have another window open and you are "focusing" (the window is active) on it. FlightGear will try to grab itself infront of the other window.

===WARNING: PUI: Too many live puInterfaces open at once!===
Appears when printing large outputs (very) frequently on the screen.

===Warning: State::drawQuads(0, 154400) too large handle in remapping to ushort glDrawElements===

[[Category:Howto|Get rid of common errors]]

[[fr:Howto: Débarrassez-vous des erreurs les plus fréquentes]]

Howto:Understand console output

2010-11-28T22:05:47Z

Airbird1: /* No image file for texture, using white */ Added more info, why it is caused.

This document lists '''[[FlightGear]] errors''', how to get rid of them and other '''console output'''. If FlightGear quits but does not give you any error, try increasing the [[FlightGear Launch Control#Debugging|Log Level]].

Errors can appear in various locations, but the most common one is the console (a black window), which pops up when you run fgfs.exe.

==Errors with known solutions==
===Airports/.... ... Done===
This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG_SCENERY]]/Airports</tt> directory.

===Base package check failed ... Found version [none] at: ... Please upgrade to version:===
* FlightGear was unable to find the [[$FG_ROOT]] directory. Set it using the <tt>--fg-root=</tt> commandline option.
* When using [[CVS]] with binaries, the data must match the binary. You cannot use data from a different date than the binary's release date.

===condition: comparison without property[1] or value===
A condition (like <tt><less-than></tt> or <tt><equals></tt>) exists, without either:
* a property to check
* a value to check the property against

===Could not find at least one of the following objects for animation:===
This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. If you are not the aircraft's author you can safely ignore such warnings.

===creating 3D noise texture... DONE===
Tells you that a new noise texture is created. It is not an error and can be ignored.

===Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified====
Try changing the [[FlightGear Launch Control#Page Four - Options and Run|BPP]] value of your FlightGear setup. If that does not work, your graphics card is probably not able to run FlightGear 1.9 and higher. Another graphics card, or an older FlightGear version will likely "fix" the problem.

===Error: bind() failed in make_server_socket()===
When using [[Howto: Multiplayer|multiplayer]] or socket input, this usually means you specified an invalid ip address or the port is in use. Note: for multiplayer, you don't need to use the ''--multiplay=in,...'' option at all, FlightGear (since version 1.0) figures out the proper setting automatically. Only use when you know what you are doing.

===Error Building Technique: findAttr: could not find attribute bool===
Make sure that your data and source (or binary) match. They must be from the same date, to provide the best performance.

===Error: connect() failed in make_client_socket() SG_IO_OUT socket creation failed===
Your computer is not connected with the internet.

===Error: RenderTexture requires the following unsupported OpenGL extensions...===
Your graphics card doesn't support some graphics feature that FG requires. Update your drivers, change the BPP value and/or try disabling some of the visual goodies like [[3D Clouds]].

===Failed to find .... in apt.dat.gz===
You need to edit ATC/default.tower and ATC/default.atis. You can open these files with any text editor. Either remove or fix the entries containing your airports ICAO code (like KSFO).

===Failed to locate aircraft carrier = ...===
FlightGear is unable to find a [[Aircraft carrier|carrier]] under the set name. Check your commandline (<tt>--carrier=...</tt>) or the [[FlightGear Launch Control#Page Three - Airport Selection|airport page]] of the launcher.

===Failed to open file ...===
Check if the file exists on your system. If the missing file is a scenery object; be sure you have the latest [http://scenemodels.flightgear.org/download/SharedModels.tgz Shared Models] from the [[FlightGear Scenery Database]].

===Fatal error: mismatched tag ...===
In some .xml file, an opening tag (like <tt><sim></tt>) does not match its closing tag (like <tt></sim></tt>). This error is hard to track down, best method is to comment (place code between <nowiki></nowiki>) most of the aircraft. Then uncomment code one by one, until the error appears again.

===Fatal error: name must begin with alpha or '_'===
This error comes up when a property should be formed of which the name does not start with a letter of the alphabet or _. If this error only happens with certain planes, contact their authors.

===Fatal error: unclosed token===
A token (<nowiki></nowiki>) has been started, but not closes. Add <nowiki>--></nowiki> at the correct line.

===FGMultiplayMgr::MP_ProcessData: No such file or directory===
This is telling you that there's someone online on the multiplayerserver, using a plane that you do not have installed on your own system. In order to remove the error (and see the other plane) you have to install the plane that the other pilot is using.

===FGMultiplayMgr - No receiver port, Multiplayermode disabled===
FlightGear [[Howto: Multiplayer|multiplayer]] has not been set.

===FGPropertyManager::GetNode() No node found for ... In component: ... unknown property ... referenced. Aborting===
FlightGear found a reference in the [[FDM]] to a non-existing property.

===FGPropertyManager::GetNode() No node found for ... The property ... is undefined.===
FlightGear found a reference in the [[FDM]] to a non-existing property. Keep in mind that JSBSim reads the FDM from top to bottom. Properties should always be created before they are needed somewhere.

===Fgtzfile_read(): : Invalid argument Fatal error: Timezone reading failed===
This one is caused by wrong line ending in a timezone file. Solution might be to download the Timezone/time.tab file manually from [http://gitorious.org/fg/fgdata/blobs/raw/master/Timezone/zone.tab Gitorious] (Right mouseclick > Save target as) and overwrite the file in <tt>[[$FG_ROOT]]/Timezone/time.tab</tt> with it.

===Found unexpected subsystem: system exiting. JSBSim failed to load aircraft and/or engine model===
You are probably trying to run an aircraft on a out-of-date version of FlightGear. The planes on the official download page are intended to be used with the latest version of FlightGear. Usage on any older systems may not work.

===freeglut (fgfs): Unable to create direct context rendering for window 'FlightGear' This may hurt performance===
This reports that you do not have proper hardware accelerated 3D (direct rendering) configured.

===Gate ... doesn't seem to have routes associated with it===
A startup location in the [[Interactive Traffic#Ground networks|groundnetwork]] is not (properly) connected to a taxi route. Contact the airport author, or import the network to [[TaxiDraw]] and run the Verify network command to find the corrupted gate.

===glLinkProgram "" Failed===
Update your drivers; they have to support atleast OpenGL 2.0 for FlightGear 2.0 and later.

===loading scenario '...'===
This is not an error. It shows that an [[AI Systems#AI Models|AI scenario]] is loaded.

===Model not found: ...===
This one tells you that FlightGear was unable to find a certain file. The nice thing is that it also tells you excactly what file.

# Check if the file really does not exist at your computer.
# Try to locate the file in which the missing file is referenced. This is likely to be <tt>-set.xml</tt> in the root directory of the loaded [[aircraft]]. Between the <model> tags, the base model file is referenced. This file references to all other models that are displayed with the aircraft.
# Contact the aircraft author with a detailed bug-report, in which you state the excact location of the missing file and (if you found it) the file in which it is referenced.

===Nasal runtime error: nil used in numeric context===
This error is [[Nasal]] triggered by a Nasal file (the console should show what file (and line) and from where it was referenced). The Nasal script tried to do something with a [[Property Tree|property]] with an empty value. A solution is to fill the property before the Nasal is loaded. This can be done by setting the property in an [[aircraft]]'s <tt>-set.xml</tt> file or by adding a [[Nasal scripting language#Listeners and Signals|listener]] to the script.

[[Howto: Contact the developers|Contact the developers]] if this error is shown for a <tt>[[$FG_ROOT]]/Nasal/</tt> script.

===Near camera not rendering===
[[Image:Near_camera_off.png|500px]]

If you screen looks like the image above; make sure you have at least [[OSG]] version 2.7.6.

===No render bin name specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===No render bin number specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===... not a valid win32 application===
This Windows error could have various reasons to pop up. Usually, the file that is causing troubles is mentioned. Re-installing this file might solve the problem.

===OBJECT_SIGN: unsupported glyph `.'===
Check the OBJECT_SIGN lines in the .stg file of the tile that was loaded when this error showed up.

===OpenAL error <AL_INVALID_VALUE>: bind source <alGenSources> Failed to generate audio source.===
This error is probably displayed because of some misdirected audio settings in the [[aircraft]]s setup. Check the -sound.xml file of the aircraft and see if all files refered to really exist. If not, try to contact the author of the plane, so he can fix the problem in the [[FlightGear CVS|CVS]] version or solve the problem yourself and let someone commit the patch.

===OpenAL error (AL_INVALID_VALUE): constructor (alBufferData) Fatal error: Failed to buffer data.===
Disabling sound is a temporarily solution for this problem.

===osgDB ac3d reader: could not find texture...===
See [[#Failed to open file ...|Failed to open file ...]]

===osgDB ac3d reader: detected surface with less than 3 vertices!===
In one of the loaded models a non-existing surface is found. This can be a single line (sometimes used to simulate thin wires) or a fault in the model.

===Program's vertex attrib binding ..., usrAttr...===
Tells you that an effect binded certain attributes to a [[Shaders|shader]].

===QNAN===
(Q)NAN stands for (Quiet) Not A Number, produced by 0/0 or other floating point break downs. There can be various causes for this:
* Using a "flap start" value of 0 in the [[YASim]] [[FDM]]. Use some small value like 0.001 instead.

===Scaling image...===
This means a texture, whether in the scenery on your aircraft or anyone elses (when multiplayer is enabled), is not sized to powers of two. All textures in FlightGear have to be sized to power of two (eg. 16*16, 32*64, 32*1024). As of version 1.9 textures are resized automaticly, but it does slow your computer down, so it's better to resize the noted textures.

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

===The system cannot find the file specified===
If you are running Windows Vista; start by looking in <tt>C:\Users\Owner\AppData\Local\VirtualStore</tt> and seeing if you have a folder called FlightGear in there. If you do, cut-and-paste (merge) that one with <tt>C:\Program Files\Flightgear</tt> and try to launch FlightGear again.

'''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible.

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

===Traffic manager could not find airport===
There is either an airport missing from apt.dat, or there is a wrong ICAO code in a [[Interactive Traffic#Building Traffic Files|traffic file]]. An airport missing from apt.dat could be due to a recent opening.

===Unable to choose requested pixel format===
Error should be solved as of version 1.9. If not, try changing your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] and/or resolution.

===Unable to find airport details for .... in FGTower::Init()===
This error can be surpressed by disabling [[Interactive Traffic|AI Traffic]], via the AI/ATC [[menu]].

The error appears when an airport in <tt>[[$FG_ROOT]]/Airports/apt.dat.gz</tt> cannot be found in <tt>[[$FG_ROOT]]/ATC/default.tower</tt> and <tt>[[$FG_ROOT]]/ATC/default.atis</tt>. Renaming the airports in the apt.dat.gz file ór in both default ATC files will fix the problem.

===Unable to open aircraft directory===
The [[aircraft]] that you are trying to run most likely relies on another aircraft, which you did not install (yet). The error shows what aircraft, so go download that one!
=== Unexpected tag '...' found in YASim aircraft description===
FlightGear found a non-existing tag in the [[FDM]] of the aircraft you are trying to launch. If you have not changed the original aircraft, contact the aircraft author. Else, check the FDM througly for mistakes.

Also, make sure you didn't force a FDM to be loaded.
* '''Commandline:''' <tt>--fdm=...</tt> should be left out.
* '''[[FGRun]]:''' <tt>Advanced > Flight Model</tt> should be set to jsb (which will leave the whole command out of the commandline, so you can use this setting with any FDM).

=== Unknown ... aircraft: ... defaulting to C172 ===
FlightGear is unable to load the forced [[FDM]] (set through <tt>--fdm=...</tt> or via <tt>Advanced > Flight Model</tt> in [[FGRun]]) for this aircraft. FlightGear automatically picks the right FDM for each aircraft, so there is no need to set it manually, unless you know what you are doing. In the Flight Model dialog of FGRun, set the FDM to <tt>jsb</tt>; that is the "auto setting".

===Unknown exception to the main loop. Aborting... Possible cause: No such file or directory===
This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear_Launch_Control#Debugging|log level]] to debug and repeating excactly what you did when the error came up, might provide some more information on what FlightGear was doing when the error occurred.
* Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work.
* Changing the resolution to a smaller one might work as well.

===WARNING: Couldn't convert texture...===
You are trying to run an aircraft not compatible with your FlightGear version. Most of the time, this error appears when you fly an aircraft, textured with .png files on versions older than 1.9. Convert the textures manually to .rgb or upgrade your FlightGear version.

===Warning: Could not find plugin to read objects from file ...===
A library is missing from your computer. Therefore, certain fileformats cannot be read. Try to reinstall/update [[OSG]], as the libraries used by FlightGear should be part of the standard package.

===Warning: Picked up TriangleIntersect===
Reduce your [[FlightGear Launch Control#Debugging|Log Level]] to alert. Or [[Showstoppers|send the fgfs output to /dev/null (unix systems) or 2>nul (Windows)]]. The errors might still be shown, but do not affect the sim anymore.

===Warning: TangentSpaceGenerator: unknown primitive mode 9===
This is an [[OSG]] error, showing up when an effect needs tangent vectors, but polygons are not support. The error itself can be ignored, altough some [[shaders]] may look wrong. Shader developers should try to minimise the use of polygons and use triangles and quads instead.

===YASim SOLUTION FAILURE: Solution failed to converge after 10000 iterations===
Some control in the [[YASim]] [[FDM]] is too weak, according to YASim, to control the aircraft. An effectiveness tag will be required in the FDM to solve this error.

===YASim SOLUTION FAILURE: Zero length fuselage===
There is a problem in the [[FDM]]. A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.

===FGMultiplayerMgr::Open - Failed to bind receive socket===

This means FlightGear was unable to open the listening network socket required by the --multiplay=in option. Frequently this option can be omitted and FlightGear will figure out the necessary parameters automatically.
Common reasons are:
* Address given in the option does not resolve to one of the IP addresses of the local machine. This parameter should only be required if you want to fine-tune the network behavior. Omitting it directs FlightGear to listen on all local interfaces automatically. Example:
--multiplay=in,10,,5001
Notice that you still need the comma.
* The UDP port given in the option (or the default port 5000 if no option given) is already in use. Verify nothing is using the port.

==Errors without known solutions==
Please take a look at the upcoming errors and see if you know a solution to get rid of them. Your additions are greatly appreciated!

===AL Error (fx): Invalid Value at pitch and gain===

===AL Error (sound manager): Invalid Operation at update===

===AL Error (sound manager): Invalid Value at buffer add data No such buffer!===

===Failed to execute command nasal===

===Failed to tie property ... to object methods===
A JSBSim error.

===FGMultiplayMgr::MP_ProcessData - message from ... has invalid length!===

===FGMultiplayMgr::MP_ProcessData: Result too large===

===GPS: malformed route, index=1===

===Mesa 7.3 implementation error: bad texture level in r300UploadSubImage===
http://www.flightgear.org/forums/viewtopic.php?f=2&t=6706&start=0&st=0&sk=t&sd=a

===Nasal runtime error: stack overflow===

===No image file for texture, using white===
A [[Shaders|shader]] error, possibly you (or the developer) have/has not specified a texture for a surface while modeling the aircraft model in AC3D, Blender, Wings...

===No path in /sim/sound/path===

You (or the developer) have/has not specified a proper sound file in the aircraft's -set.xml file.

===OBJECT_SIGN: unexpected } in sign contents===

===OpenAL error (AL_ILLEGAL_COMMAND): set_source_pos===

Has something to do with OpenAL not understanding where the sound comes from.

===OpenAL error (AL_ILLEGAL_COMMAND): set_volume===

Has something to do with OpenAL not understanding the sound volume.

===PT_vs_hpt: ran out of layers===
This is issued from the atmosphere implementation in FlightGear's environment system. A comment in the code says: "''should never get here''". Please provide input when this happens: excessive altitudes? Negative altitudes?

===Warning: detected OpenGL error 'invalid value' after RenderBin::draw(,)===
This warning is generated from OSG. Set your environment variable
OSG_NOTIFY_LEVEL=FATAL

===Warning: GraphicsWindowWin32::grabFocus() - Failed grabbing the focus===

It seems that this happens when you have another window open and you are "focusing" (the window is active) on it. FlightGear will try to grab itself infront of the other window.

===WARNING: PUI: Too many live puInterfaces open at once!===
Appears when printing large outputs (very) frequently on the screen.

===Warning: State::drawQuads(0, 154400) too large handle in remapping to ushort glDrawElements===

[[Category:Howto|Get rid of common errors]]

[[fr:Howto: Débarrassez-vous des erreurs les plus fréquentes]]

Howto:Understand console output

2010-11-28T22:02:13Z

Airbird1: /* OpenAL error (AL_ILLEGAL_COMMAND): set_volume */ Added opinion

This document lists '''[[FlightGear]] errors''', how to get rid of them and other '''console output'''. If FlightGear quits but does not give you any error, try increasing the [[FlightGear Launch Control#Debugging|Log Level]].

Errors can appear in various locations, but the most common one is the console (a black window), which pops up when you run fgfs.exe.

==Errors with known solutions==
===Airports/.... ... Done===
This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG_SCENERY]]/Airports</tt> directory.

===Base package check failed ... Found version [none] at: ... Please upgrade to version:===
* FlightGear was unable to find the [[$FG_ROOT]] directory. Set it using the <tt>--fg-root=</tt> commandline option.
* When using [[CVS]] with binaries, the data must match the binary. You cannot use data from a different date than the binary's release date.

===condition: comparison without property[1] or value===
A condition (like <tt><less-than></tt> or <tt><equals></tt>) exists, without either:
* a property to check
* a value to check the property against

===Could not find at least one of the following objects for animation:===
This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. If you are not the aircraft's author you can safely ignore such warnings.

===creating 3D noise texture... DONE===
Tells you that a new noise texture is created. It is not an error and can be ignored.

===Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified====
Try changing the [[FlightGear Launch Control#Page Four - Options and Run|BPP]] value of your FlightGear setup. If that does not work, your graphics card is probably not able to run FlightGear 1.9 and higher. Another graphics card, or an older FlightGear version will likely "fix" the problem.

===Error: bind() failed in make_server_socket()===
When using [[Howto: Multiplayer|multiplayer]] or socket input, this usually means you specified an invalid ip address or the port is in use. Note: for multiplayer, you don't need to use the ''--multiplay=in,...'' option at all, FlightGear (since version 1.0) figures out the proper setting automatically. Only use when you know what you are doing.

===Error Building Technique: findAttr: could not find attribute bool===
Make sure that your data and source (or binary) match. They must be from the same date, to provide the best performance.

===Error: connect() failed in make_client_socket() SG_IO_OUT socket creation failed===
Your computer is not connected with the internet.

===Error: RenderTexture requires the following unsupported OpenGL extensions...===
Your graphics card doesn't support some graphics feature that FG requires. Update your drivers, change the BPP value and/or try disabling some of the visual goodies like [[3D Clouds]].

===Failed to find .... in apt.dat.gz===
You need to edit ATC/default.tower and ATC/default.atis. You can open these files with any text editor. Either remove or fix the entries containing your airports ICAO code (like KSFO).

===Failed to locate aircraft carrier = ...===
FlightGear is unable to find a [[Aircraft carrier|carrier]] under the set name. Check your commandline (<tt>--carrier=...</tt>) or the [[FlightGear Launch Control#Page Three - Airport Selection|airport page]] of the launcher.

===Failed to open file ...===
Check if the file exists on your system. If the missing file is a scenery object; be sure you have the latest [http://scenemodels.flightgear.org/download/SharedModels.tgz Shared Models] from the [[FlightGear Scenery Database]].

===Fatal error: mismatched tag ...===
In some .xml file, an opening tag (like <tt><sim></tt>) does not match its closing tag (like <tt></sim></tt>). This error is hard to track down, best method is to comment (place code between <nowiki></nowiki>) most of the aircraft. Then uncomment code one by one, until the error appears again.

===Fatal error: name must begin with alpha or '_'===
This error comes up when a property should be formed of which the name does not start with a letter of the alphabet or _. If this error only happens with certain planes, contact their authors.

===Fatal error: unclosed token===
A token (<nowiki></nowiki>) has been started, but not closes. Add <nowiki>--></nowiki> at the correct line.

===FGMultiplayMgr::MP_ProcessData: No such file or directory===
This is telling you that there's someone online on the multiplayerserver, using a plane that you do not have installed on your own system. In order to remove the error (and see the other plane) you have to install the plane that the other pilot is using.

===FGMultiplayMgr - No receiver port, Multiplayermode disabled===
FlightGear [[Howto: Multiplayer|multiplayer]] has not been set.

===FGPropertyManager::GetNode() No node found for ... In component: ... unknown property ... referenced. Aborting===
FlightGear found a reference in the [[FDM]] to a non-existing property.

===FGPropertyManager::GetNode() No node found for ... The property ... is undefined.===
FlightGear found a reference in the [[FDM]] to a non-existing property. Keep in mind that JSBSim reads the FDM from top to bottom. Properties should always be created before they are needed somewhere.

===Fgtzfile_read(): : Invalid argument Fatal error: Timezone reading failed===
This one is caused by wrong line ending in a timezone file. Solution might be to download the Timezone/time.tab file manually from [http://gitorious.org/fg/fgdata/blobs/raw/master/Timezone/zone.tab Gitorious] (Right mouseclick > Save target as) and overwrite the file in <tt>[[$FG_ROOT]]/Timezone/time.tab</tt> with it.

===Found unexpected subsystem: system exiting. JSBSim failed to load aircraft and/or engine model===
You are probably trying to run an aircraft on a out-of-date version of FlightGear. The planes on the official download page are intended to be used with the latest version of FlightGear. Usage on any older systems may not work.

===freeglut (fgfs): Unable to create direct context rendering for window 'FlightGear' This may hurt performance===
This reports that you do not have proper hardware accelerated 3D (direct rendering) configured.

===Gate ... doesn't seem to have routes associated with it===
A startup location in the [[Interactive Traffic#Ground networks|groundnetwork]] is not (properly) connected to a taxi route. Contact the airport author, or import the network to [[TaxiDraw]] and run the Verify network command to find the corrupted gate.

===glLinkProgram "" Failed===
Update your drivers; they have to support atleast OpenGL 2.0 for FlightGear 2.0 and later.

===loading scenario '...'===
This is not an error. It shows that an [[AI Systems#AI Models|AI scenario]] is loaded.

===Model not found: ...===
This one tells you that FlightGear was unable to find a certain file. The nice thing is that it also tells you excactly what file.

# Check if the file really does not exist at your computer.
# Try to locate the file in which the missing file is referenced. This is likely to be <tt>-set.xml</tt> in the root directory of the loaded [[aircraft]]. Between the <model> tags, the base model file is referenced. This file references to all other models that are displayed with the aircraft.
# Contact the aircraft author with a detailed bug-report, in which you state the excact location of the missing file and (if you found it) the file in which it is referenced.

===Nasal runtime error: nil used in numeric context===
This error is [[Nasal]] triggered by a Nasal file (the console should show what file (and line) and from where it was referenced). The Nasal script tried to do something with a [[Property Tree|property]] with an empty value. A solution is to fill the property before the Nasal is loaded. This can be done by setting the property in an [[aircraft]]'s <tt>-set.xml</tt> file or by adding a [[Nasal scripting language#Listeners and Signals|listener]] to the script.

[[Howto: Contact the developers|Contact the developers]] if this error is shown for a <tt>[[$FG_ROOT]]/Nasal/</tt> script.

===Near camera not rendering===
[[Image:Near_camera_off.png|500px]]

If you screen looks like the image above; make sure you have at least [[OSG]] version 2.7.6.

===No render bin name specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===No render bin number specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===... not a valid win32 application===
This Windows error could have various reasons to pop up. Usually, the file that is causing troubles is mentioned. Re-installing this file might solve the problem.

===OBJECT_SIGN: unsupported glyph `.'===
Check the OBJECT_SIGN lines in the .stg file of the tile that was loaded when this error showed up.

===OpenAL error <AL_INVALID_VALUE>: bind source <alGenSources> Failed to generate audio source.===
This error is probably displayed because of some misdirected audio settings in the [[aircraft]]s setup. Check the -sound.xml file of the aircraft and see if all files refered to really exist. If not, try to contact the author of the plane, so he can fix the problem in the [[FlightGear CVS|CVS]] version or solve the problem yourself and let someone commit the patch.

===OpenAL error (AL_INVALID_VALUE): constructor (alBufferData) Fatal error: Failed to buffer data.===
Disabling sound is a temporarily solution for this problem.

===osgDB ac3d reader: could not find texture...===
See [[#Failed to open file ...|Failed to open file ...]]

===osgDB ac3d reader: detected surface with less than 3 vertices!===
In one of the loaded models a non-existing surface is found. This can be a single line (sometimes used to simulate thin wires) or a fault in the model.

===Program's vertex attrib binding ..., usrAttr...===
Tells you that an effect binded certain attributes to a [[Shaders|shader]].

===QNAN===
(Q)NAN stands for (Quiet) Not A Number, produced by 0/0 or other floating point break downs. There can be various causes for this:
* Using a "flap start" value of 0 in the [[YASim]] [[FDM]]. Use some small value like 0.001 instead.

===Scaling image...===
This means a texture, whether in the scenery on your aircraft or anyone elses (when multiplayer is enabled), is not sized to powers of two. All textures in FlightGear have to be sized to power of two (eg. 16*16, 32*64, 32*1024). As of version 1.9 textures are resized automaticly, but it does slow your computer down, so it's better to resize the noted textures.

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

===The system cannot find the file specified===
If you are running Windows Vista; start by looking in <tt>C:\Users\Owner\AppData\Local\VirtualStore</tt> and seeing if you have a folder called FlightGear in there. If you do, cut-and-paste (merge) that one with <tt>C:\Program Files\Flightgear</tt> and try to launch FlightGear again.

'''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible.

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

===Traffic manager could not find airport===
There is either an airport missing from apt.dat, or there is a wrong ICAO code in a [[Interactive Traffic#Building Traffic Files|traffic file]]. An airport missing from apt.dat could be due to a recent opening.

===Unable to choose requested pixel format===
Error should be solved as of version 1.9. If not, try changing your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] and/or resolution.

===Unable to find airport details for .... in FGTower::Init()===
This error can be surpressed by disabling [[Interactive Traffic|AI Traffic]], via the AI/ATC [[menu]].

The error appears when an airport in <tt>[[$FG_ROOT]]/Airports/apt.dat.gz</tt> cannot be found in <tt>[[$FG_ROOT]]/ATC/default.tower</tt> and <tt>[[$FG_ROOT]]/ATC/default.atis</tt>. Renaming the airports in the apt.dat.gz file ór in both default ATC files will fix the problem.

===Unable to open aircraft directory===
The [[aircraft]] that you are trying to run most likely relies on another aircraft, which you did not install (yet). The error shows what aircraft, so go download that one!
=== Unexpected tag '...' found in YASim aircraft description===
FlightGear found a non-existing tag in the [[FDM]] of the aircraft you are trying to launch. If you have not changed the original aircraft, contact the aircraft author. Else, check the FDM througly for mistakes.

Also, make sure you didn't force a FDM to be loaded.
* '''Commandline:''' <tt>--fdm=...</tt> should be left out.
* '''[[FGRun]]:''' <tt>Advanced > Flight Model</tt> should be set to jsb (which will leave the whole command out of the commandline, so you can use this setting with any FDM).

=== Unknown ... aircraft: ... defaulting to C172 ===
FlightGear is unable to load the forced [[FDM]] (set through <tt>--fdm=...</tt> or via <tt>Advanced > Flight Model</tt> in [[FGRun]]) for this aircraft. FlightGear automatically picks the right FDM for each aircraft, so there is no need to set it manually, unless you know what you are doing. In the Flight Model dialog of FGRun, set the FDM to <tt>jsb</tt>; that is the "auto setting".

===Unknown exception to the main loop. Aborting... Possible cause: No such file or directory===
This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear_Launch_Control#Debugging|log level]] to debug and repeating excactly what you did when the error came up, might provide some more information on what FlightGear was doing when the error occurred.
* Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work.
* Changing the resolution to a smaller one might work as well.

===WARNING: Couldn't convert texture...===
You are trying to run an aircraft not compatible with your FlightGear version. Most of the time, this error appears when you fly an aircraft, textured with .png files on versions older than 1.9. Convert the textures manually to .rgb or upgrade your FlightGear version.

===Warning: Could not find plugin to read objects from file ...===
A library is missing from your computer. Therefore, certain fileformats cannot be read. Try to reinstall/update [[OSG]], as the libraries used by FlightGear should be part of the standard package.

===Warning: Picked up TriangleIntersect===
Reduce your [[FlightGear Launch Control#Debugging|Log Level]] to alert. Or [[Showstoppers|send the fgfs output to /dev/null (unix systems) or 2>nul (Windows)]]. The errors might still be shown, but do not affect the sim anymore.

===Warning: TangentSpaceGenerator: unknown primitive mode 9===
This is an [[OSG]] error, showing up when an effect needs tangent vectors, but polygons are not support. The error itself can be ignored, altough some [[shaders]] may look wrong. Shader developers should try to minimise the use of polygons and use triangles and quads instead.

===YASim SOLUTION FAILURE: Solution failed to converge after 10000 iterations===
Some control in the [[YASim]] [[FDM]] is too weak, according to YASim, to control the aircraft. An effectiveness tag will be required in the FDM to solve this error.

===YASim SOLUTION FAILURE: Zero length fuselage===
There is a problem in the [[FDM]]. A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.

===FGMultiplayerMgr::Open - Failed to bind receive socket===

This means FlightGear was unable to open the listening network socket required by the --multiplay=in option. Frequently this option can be omitted and FlightGear will figure out the necessary parameters automatically.
Common reasons are:
* Address given in the option does not resolve to one of the IP addresses of the local machine. This parameter should only be required if you want to fine-tune the network behavior. Omitting it directs FlightGear to listen on all local interfaces automatically. Example:
--multiplay=in,10,,5001
Notice that you still need the comma.
* The UDP port given in the option (or the default port 5000 if no option given) is already in use. Verify nothing is using the port.

==Errors without known solutions==
Please take a look at the upcoming errors and see if you know a solution to get rid of them. Your additions are greatly appreciated!

===AL Error (fx): Invalid Value at pitch and gain===

===AL Error (sound manager): Invalid Operation at update===

===AL Error (sound manager): Invalid Value at buffer add data No such buffer!===

===Failed to execute command nasal===

===Failed to tie property ... to object methods===
A JSBSim error.

===FGMultiplayMgr::MP_ProcessData - message from ... has invalid length!===

===FGMultiplayMgr::MP_ProcessData: Result too large===

===GPS: malformed route, index=1===

===Mesa 7.3 implementation error: bad texture level in r300UploadSubImage===
http://www.flightgear.org/forums/viewtopic.php?f=2&t=6706&start=0&st=0&sk=t&sd=a

===Nasal runtime error: stack overflow===

===No image file for texture, using white===
A [[Shaders|shader]] error

===No path in /sim/sound/path===

You (or the developer) have/has not specified a proper sound file in the aircraft's -set.xml file.

===OBJECT_SIGN: unexpected } in sign contents===

===OpenAL error (AL_ILLEGAL_COMMAND): set_source_pos===

Has something to do with OpenAL not understanding where the sound comes from.

===OpenAL error (AL_ILLEGAL_COMMAND): set_volume===

Has something to do with OpenAL not understanding the sound volume.

===PT_vs_hpt: ran out of layers===
This is issued from the atmosphere implementation in FlightGear's environment system. A comment in the code says: "''should never get here''". Please provide input when this happens: excessive altitudes? Negative altitudes?

===Warning: detected OpenGL error 'invalid value' after RenderBin::draw(,)===
This warning is generated from OSG. Set your environment variable
OSG_NOTIFY_LEVEL=FATAL

===Warning: GraphicsWindowWin32::grabFocus() - Failed grabbing the focus===

It seems that this happens when you have another window open and you are "focusing" (the window is active) on it. FlightGear will try to grab itself infront of the other window.

===WARNING: PUI: Too many live puInterfaces open at once!===
Appears when printing large outputs (very) frequently on the screen.

===Warning: State::drawQuads(0, 154400) too large handle in remapping to ushort glDrawElements===

[[Category:Howto|Get rid of common errors]]

[[fr:Howto: Débarrassez-vous des erreurs les plus fréquentes]]

Howto:Understand console output

2010-11-28T22:01:23Z

Airbird1: /* OpenAL error (AL_ILLEGAL_COMMAND): set_source_pos */

This document lists '''[[FlightGear]] errors''', how to get rid of them and other '''console output'''. If FlightGear quits but does not give you any error, try increasing the [[FlightGear Launch Control#Debugging|Log Level]].

Errors can appear in various locations, but the most common one is the console (a black window), which pops up when you run fgfs.exe.

==Errors with known solutions==
===Airports/.... ... Done===
This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG_SCENERY]]/Airports</tt> directory.

===Base package check failed ... Found version [none] at: ... Please upgrade to version:===
* FlightGear was unable to find the [[$FG_ROOT]] directory. Set it using the <tt>--fg-root=</tt> commandline option.
* When using [[CVS]] with binaries, the data must match the binary. You cannot use data from a different date than the binary's release date.

===condition: comparison without property[1] or value===
A condition (like <tt><less-than></tt> or <tt><equals></tt>) exists, without either:
* a property to check
* a value to check the property against

===Could not find at least one of the following objects for animation:===
This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. If you are not the aircraft's author you can safely ignore such warnings.

===creating 3D noise texture... DONE===
Tells you that a new noise texture is created. It is not an error and can be ignored.

===Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified====
Try changing the [[FlightGear Launch Control#Page Four - Options and Run|BPP]] value of your FlightGear setup. If that does not work, your graphics card is probably not able to run FlightGear 1.9 and higher. Another graphics card, or an older FlightGear version will likely "fix" the problem.

===Error: bind() failed in make_server_socket()===
When using [[Howto: Multiplayer|multiplayer]] or socket input, this usually means you specified an invalid ip address or the port is in use. Note: for multiplayer, you don't need to use the ''--multiplay=in,...'' option at all, FlightGear (since version 1.0) figures out the proper setting automatically. Only use when you know what you are doing.

===Error Building Technique: findAttr: could not find attribute bool===
Make sure that your data and source (or binary) match. They must be from the same date, to provide the best performance.

===Error: connect() failed in make_client_socket() SG_IO_OUT socket creation failed===
Your computer is not connected with the internet.

===Error: RenderTexture requires the following unsupported OpenGL extensions...===
Your graphics card doesn't support some graphics feature that FG requires. Update your drivers, change the BPP value and/or try disabling some of the visual goodies like [[3D Clouds]].

===Failed to find .... in apt.dat.gz===
You need to edit ATC/default.tower and ATC/default.atis. You can open these files with any text editor. Either remove or fix the entries containing your airports ICAO code (like KSFO).

===Failed to locate aircraft carrier = ...===
FlightGear is unable to find a [[Aircraft carrier|carrier]] under the set name. Check your commandline (<tt>--carrier=...</tt>) or the [[FlightGear Launch Control#Page Three - Airport Selection|airport page]] of the launcher.

===Failed to open file ...===
Check if the file exists on your system. If the missing file is a scenery object; be sure you have the latest [http://scenemodels.flightgear.org/download/SharedModels.tgz Shared Models] from the [[FlightGear Scenery Database]].

===Fatal error: mismatched tag ...===
In some .xml file, an opening tag (like <tt><sim></tt>) does not match its closing tag (like <tt></sim></tt>). This error is hard to track down, best method is to comment (place code between <nowiki></nowiki>) most of the aircraft. Then uncomment code one by one, until the error appears again.

===Fatal error: name must begin with alpha or '_'===
This error comes up when a property should be formed of which the name does not start with a letter of the alphabet or _. If this error only happens with certain planes, contact their authors.

===Fatal error: unclosed token===
A token (<nowiki></nowiki>) has been started, but not closes. Add <nowiki>--></nowiki> at the correct line.

===FGMultiplayMgr::MP_ProcessData: No such file or directory===
This is telling you that there's someone online on the multiplayerserver, using a plane that you do not have installed on your own system. In order to remove the error (and see the other plane) you have to install the plane that the other pilot is using.

===FGMultiplayMgr - No receiver port, Multiplayermode disabled===
FlightGear [[Howto: Multiplayer|multiplayer]] has not been set.

===FGPropertyManager::GetNode() No node found for ... In component: ... unknown property ... referenced. Aborting===
FlightGear found a reference in the [[FDM]] to a non-existing property.

===FGPropertyManager::GetNode() No node found for ... The property ... is undefined.===
FlightGear found a reference in the [[FDM]] to a non-existing property. Keep in mind that JSBSim reads the FDM from top to bottom. Properties should always be created before they are needed somewhere.

===Fgtzfile_read(): : Invalid argument Fatal error: Timezone reading failed===
This one is caused by wrong line ending in a timezone file. Solution might be to download the Timezone/time.tab file manually from [http://gitorious.org/fg/fgdata/blobs/raw/master/Timezone/zone.tab Gitorious] (Right mouseclick > Save target as) and overwrite the file in <tt>[[$FG_ROOT]]/Timezone/time.tab</tt> with it.

===Found unexpected subsystem: system exiting. JSBSim failed to load aircraft and/or engine model===
You are probably trying to run an aircraft on a out-of-date version of FlightGear. The planes on the official download page are intended to be used with the latest version of FlightGear. Usage on any older systems may not work.

===freeglut (fgfs): Unable to create direct context rendering for window 'FlightGear' This may hurt performance===
This reports that you do not have proper hardware accelerated 3D (direct rendering) configured.

===Gate ... doesn't seem to have routes associated with it===
A startup location in the [[Interactive Traffic#Ground networks|groundnetwork]] is not (properly) connected to a taxi route. Contact the airport author, or import the network to [[TaxiDraw]] and run the Verify network command to find the corrupted gate.

===glLinkProgram "" Failed===
Update your drivers; they have to support atleast OpenGL 2.0 for FlightGear 2.0 and later.

===loading scenario '...'===
This is not an error. It shows that an [[AI Systems#AI Models|AI scenario]] is loaded.

===Model not found: ...===
This one tells you that FlightGear was unable to find a certain file. The nice thing is that it also tells you excactly what file.

# Check if the file really does not exist at your computer.
# Try to locate the file in which the missing file is referenced. This is likely to be <tt>-set.xml</tt> in the root directory of the loaded [[aircraft]]. Between the <model> tags, the base model file is referenced. This file references to all other models that are displayed with the aircraft.
# Contact the aircraft author with a detailed bug-report, in which you state the excact location of the missing file and (if you found it) the file in which it is referenced.

===Nasal runtime error: nil used in numeric context===
This error is [[Nasal]] triggered by a Nasal file (the console should show what file (and line) and from where it was referenced). The Nasal script tried to do something with a [[Property Tree|property]] with an empty value. A solution is to fill the property before the Nasal is loaded. This can be done by setting the property in an [[aircraft]]'s <tt>-set.xml</tt> file or by adding a [[Nasal scripting language#Listeners and Signals|listener]] to the script.

[[Howto: Contact the developers|Contact the developers]] if this error is shown for a <tt>[[$FG_ROOT]]/Nasal/</tt> script.

===Near camera not rendering===
[[Image:Near_camera_off.png|500px]]

If you screen looks like the image above; make sure you have at least [[OSG]] version 2.7.6.

===No render bin name specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===No render bin number specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===... not a valid win32 application===
This Windows error could have various reasons to pop up. Usually, the file that is causing troubles is mentioned. Re-installing this file might solve the problem.

===OBJECT_SIGN: unsupported glyph `.'===
Check the OBJECT_SIGN lines in the .stg file of the tile that was loaded when this error showed up.

===OpenAL error <AL_INVALID_VALUE>: bind source <alGenSources> Failed to generate audio source.===
This error is probably displayed because of some misdirected audio settings in the [[aircraft]]s setup. Check the -sound.xml file of the aircraft and see if all files refered to really exist. If not, try to contact the author of the plane, so he can fix the problem in the [[FlightGear CVS|CVS]] version or solve the problem yourself and let someone commit the patch.

===OpenAL error (AL_INVALID_VALUE): constructor (alBufferData) Fatal error: Failed to buffer data.===
Disabling sound is a temporarily solution for this problem.

===osgDB ac3d reader: could not find texture...===
See [[#Failed to open file ...|Failed to open file ...]]

===osgDB ac3d reader: detected surface with less than 3 vertices!===
In one of the loaded models a non-existing surface is found. This can be a single line (sometimes used to simulate thin wires) or a fault in the model.

===Program's vertex attrib binding ..., usrAttr...===
Tells you that an effect binded certain attributes to a [[Shaders|shader]].

===QNAN===
(Q)NAN stands for (Quiet) Not A Number, produced by 0/0 or other floating point break downs. There can be various causes for this:
* Using a "flap start" value of 0 in the [[YASim]] [[FDM]]. Use some small value like 0.001 instead.

===Scaling image...===
This means a texture, whether in the scenery on your aircraft or anyone elses (when multiplayer is enabled), is not sized to powers of two. All textures in FlightGear have to be sized to power of two (eg. 16*16, 32*64, 32*1024). As of version 1.9 textures are resized automaticly, but it does slow your computer down, so it's better to resize the noted textures.

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

===The system cannot find the file specified===
If you are running Windows Vista; start by looking in <tt>C:\Users\Owner\AppData\Local\VirtualStore</tt> and seeing if you have a folder called FlightGear in there. If you do, cut-and-paste (merge) that one with <tt>C:\Program Files\Flightgear</tt> and try to launch FlightGear again.

'''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible.

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

===Traffic manager could not find airport===
There is either an airport missing from apt.dat, or there is a wrong ICAO code in a [[Interactive Traffic#Building Traffic Files|traffic file]]. An airport missing from apt.dat could be due to a recent opening.

===Unable to choose requested pixel format===
Error should be solved as of version 1.9. If not, try changing your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] and/or resolution.

===Unable to find airport details for .... in FGTower::Init()===
This error can be surpressed by disabling [[Interactive Traffic|AI Traffic]], via the AI/ATC [[menu]].

The error appears when an airport in <tt>[[$FG_ROOT]]/Airports/apt.dat.gz</tt> cannot be found in <tt>[[$FG_ROOT]]/ATC/default.tower</tt> and <tt>[[$FG_ROOT]]/ATC/default.atis</tt>. Renaming the airports in the apt.dat.gz file ór in both default ATC files will fix the problem.

===Unable to open aircraft directory===
The [[aircraft]] that you are trying to run most likely relies on another aircraft, which you did not install (yet). The error shows what aircraft, so go download that one!
=== Unexpected tag '...' found in YASim aircraft description===
FlightGear found a non-existing tag in the [[FDM]] of the aircraft you are trying to launch. If you have not changed the original aircraft, contact the aircraft author. Else, check the FDM througly for mistakes.

Also, make sure you didn't force a FDM to be loaded.
* '''Commandline:''' <tt>--fdm=...</tt> should be left out.
* '''[[FGRun]]:''' <tt>Advanced > Flight Model</tt> should be set to jsb (which will leave the whole command out of the commandline, so you can use this setting with any FDM).

=== Unknown ... aircraft: ... defaulting to C172 ===
FlightGear is unable to load the forced [[FDM]] (set through <tt>--fdm=...</tt> or via <tt>Advanced > Flight Model</tt> in [[FGRun]]) for this aircraft. FlightGear automatically picks the right FDM for each aircraft, so there is no need to set it manually, unless you know what you are doing. In the Flight Model dialog of FGRun, set the FDM to <tt>jsb</tt>; that is the "auto setting".

===Unknown exception to the main loop. Aborting... Possible cause: No such file or directory===
This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear_Launch_Control#Debugging|log level]] to debug and repeating excactly what you did when the error came up, might provide some more information on what FlightGear was doing when the error occurred.
* Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work.
* Changing the resolution to a smaller one might work as well.

===WARNING: Couldn't convert texture...===
You are trying to run an aircraft not compatible with your FlightGear version. Most of the time, this error appears when you fly an aircraft, textured with .png files on versions older than 1.9. Convert the textures manually to .rgb or upgrade your FlightGear version.

===Warning: Could not find plugin to read objects from file ...===
A library is missing from your computer. Therefore, certain fileformats cannot be read. Try to reinstall/update [[OSG]], as the libraries used by FlightGear should be part of the standard package.

===Warning: Picked up TriangleIntersect===
Reduce your [[FlightGear Launch Control#Debugging|Log Level]] to alert. Or [[Showstoppers|send the fgfs output to /dev/null (unix systems) or 2>nul (Windows)]]. The errors might still be shown, but do not affect the sim anymore.

===Warning: TangentSpaceGenerator: unknown primitive mode 9===
This is an [[OSG]] error, showing up when an effect needs tangent vectors, but polygons are not support. The error itself can be ignored, altough some [[shaders]] may look wrong. Shader developers should try to minimise the use of polygons and use triangles and quads instead.

===YASim SOLUTION FAILURE: Solution failed to converge after 10000 iterations===
Some control in the [[YASim]] [[FDM]] is too weak, according to YASim, to control the aircraft. An effectiveness tag will be required in the FDM to solve this error.

===YASim SOLUTION FAILURE: Zero length fuselage===
There is a problem in the [[FDM]]. A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.

===FGMultiplayerMgr::Open - Failed to bind receive socket===

This means FlightGear was unable to open the listening network socket required by the --multiplay=in option. Frequently this option can be omitted and FlightGear will figure out the necessary parameters automatically.
Common reasons are:
* Address given in the option does not resolve to one of the IP addresses of the local machine. This parameter should only be required if you want to fine-tune the network behavior. Omitting it directs FlightGear to listen on all local interfaces automatically. Example:
--multiplay=in,10,,5001
Notice that you still need the comma.
* The UDP port given in the option (or the default port 5000 if no option given) is already in use. Verify nothing is using the port.

==Errors without known solutions==
Please take a look at the upcoming errors and see if you know a solution to get rid of them. Your additions are greatly appreciated!

===AL Error (fx): Invalid Value at pitch and gain===

===AL Error (sound manager): Invalid Operation at update===

===AL Error (sound manager): Invalid Value at buffer add data No such buffer!===

===Failed to execute command nasal===

===Failed to tie property ... to object methods===
A JSBSim error.

===FGMultiplayMgr::MP_ProcessData - message from ... has invalid length!===

===FGMultiplayMgr::MP_ProcessData: Result too large===

===GPS: malformed route, index=1===

===Mesa 7.3 implementation error: bad texture level in r300UploadSubImage===
http://www.flightgear.org/forums/viewtopic.php?f=2&t=6706&start=0&st=0&sk=t&sd=a

===Nasal runtime error: stack overflow===

===No image file for texture, using white===
A [[Shaders|shader]] error

===No path in /sim/sound/path===

You (or the developer) have/has not specified a proper sound file in the aircraft's -set.xml file.

===OBJECT_SIGN: unexpected } in sign contents===

===OpenAL error (AL_ILLEGAL_COMMAND): set_source_pos===

Has something to do with OpenAL not understanding where the sound comes from.

===OpenAL error (AL_ILLEGAL_COMMAND): set_volume===

===PT_vs_hpt: ran out of layers===
This is issued from the atmosphere implementation in FlightGear's environment system. A comment in the code says: "''should never get here''". Please provide input when this happens: excessive altitudes? Negative altitudes?

===Warning: detected OpenGL error 'invalid value' after RenderBin::draw(,)===
This warning is generated from OSG. Set your environment variable
OSG_NOTIFY_LEVEL=FATAL

===Warning: GraphicsWindowWin32::grabFocus() - Failed grabbing the focus===

It seems that this happens when you have another window open and you are "focusing" (the window is active) on it. FlightGear will try to grab itself infront of the other window.

===WARNING: PUI: Too many live puInterfaces open at once!===
Appears when printing large outputs (very) frequently on the screen.

===Warning: State::drawQuads(0, 154400) too large handle in remapping to ushort glDrawElements===

[[Category:Howto|Get rid of common errors]]

[[fr:Howto: Débarrassez-vous des erreurs les plus fréquentes]]

Howto:Understand console output

2010-11-28T21:59:40Z

Airbird1: /* No path in /sim/sound/path */ Added explanation

This document lists '''[[FlightGear]] errors''', how to get rid of them and other '''console output'''. If FlightGear quits but does not give you any error, try increasing the [[FlightGear Launch Control#Debugging|Log Level]].

Errors can appear in various locations, but the most common one is the console (a black window), which pops up when you run fgfs.exe.

==Errors with known solutions==
===Airports/.... ... Done===
This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG_SCENERY]]/Airports</tt> directory.

===Base package check failed ... Found version [none] at: ... Please upgrade to version:===
* FlightGear was unable to find the [[$FG_ROOT]] directory. Set it using the <tt>--fg-root=</tt> commandline option.
* When using [[CVS]] with binaries, the data must match the binary. You cannot use data from a different date than the binary's release date.

===condition: comparison without property[1] or value===
A condition (like <tt><less-than></tt> or <tt><equals></tt>) exists, without either:
* a property to check
* a value to check the property against

===Could not find at least one of the following objects for animation:===
This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. If you are not the aircraft's author you can safely ignore such warnings.

===creating 3D noise texture... DONE===
Tells you that a new noise texture is created. It is not an error and can be ignored.

===Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified====
Try changing the [[FlightGear Launch Control#Page Four - Options and Run|BPP]] value of your FlightGear setup. If that does not work, your graphics card is probably not able to run FlightGear 1.9 and higher. Another graphics card, or an older FlightGear version will likely "fix" the problem.

===Error: bind() failed in make_server_socket()===
When using [[Howto: Multiplayer|multiplayer]] or socket input, this usually means you specified an invalid ip address or the port is in use. Note: for multiplayer, you don't need to use the ''--multiplay=in,...'' option at all, FlightGear (since version 1.0) figures out the proper setting automatically. Only use when you know what you are doing.

===Error Building Technique: findAttr: could not find attribute bool===
Make sure that your data and source (or binary) match. They must be from the same date, to provide the best performance.

===Error: connect() failed in make_client_socket() SG_IO_OUT socket creation failed===
Your computer is not connected with the internet.

===Error: RenderTexture requires the following unsupported OpenGL extensions...===
Your graphics card doesn't support some graphics feature that FG requires. Update your drivers, change the BPP value and/or try disabling some of the visual goodies like [[3D Clouds]].

===Failed to find .... in apt.dat.gz===
You need to edit ATC/default.tower and ATC/default.atis. You can open these files with any text editor. Either remove or fix the entries containing your airports ICAO code (like KSFO).

===Failed to locate aircraft carrier = ...===
FlightGear is unable to find a [[Aircraft carrier|carrier]] under the set name. Check your commandline (<tt>--carrier=...</tt>) or the [[FlightGear Launch Control#Page Three - Airport Selection|airport page]] of the launcher.

===Failed to open file ...===
Check if the file exists on your system. If the missing file is a scenery object; be sure you have the latest [http://scenemodels.flightgear.org/download/SharedModels.tgz Shared Models] from the [[FlightGear Scenery Database]].

===Fatal error: mismatched tag ...===
In some .xml file, an opening tag (like <tt><sim></tt>) does not match its closing tag (like <tt></sim></tt>). This error is hard to track down, best method is to comment (place code between <nowiki></nowiki>) most of the aircraft. Then uncomment code one by one, until the error appears again.

===Fatal error: name must begin with alpha or '_'===
This error comes up when a property should be formed of which the name does not start with a letter of the alphabet or _. If this error only happens with certain planes, contact their authors.

===Fatal error: unclosed token===
A token (<nowiki></nowiki>) has been started, but not closes. Add <nowiki>--></nowiki> at the correct line.

===FGMultiplayMgr::MP_ProcessData: No such file or directory===
This is telling you that there's someone online on the multiplayerserver, using a plane that you do not have installed on your own system. In order to remove the error (and see the other plane) you have to install the plane that the other pilot is using.

===FGMultiplayMgr - No receiver port, Multiplayermode disabled===
FlightGear [[Howto: Multiplayer|multiplayer]] has not been set.

===FGPropertyManager::GetNode() No node found for ... In component: ... unknown property ... referenced. Aborting===
FlightGear found a reference in the [[FDM]] to a non-existing property.

===FGPropertyManager::GetNode() No node found for ... The property ... is undefined.===
FlightGear found a reference in the [[FDM]] to a non-existing property. Keep in mind that JSBSim reads the FDM from top to bottom. Properties should always be created before they are needed somewhere.

===Fgtzfile_read(): : Invalid argument Fatal error: Timezone reading failed===
This one is caused by wrong line ending in a timezone file. Solution might be to download the Timezone/time.tab file manually from [http://gitorious.org/fg/fgdata/blobs/raw/master/Timezone/zone.tab Gitorious] (Right mouseclick > Save target as) and overwrite the file in <tt>[[$FG_ROOT]]/Timezone/time.tab</tt> with it.

===Found unexpected subsystem: system exiting. JSBSim failed to load aircraft and/or engine model===
You are probably trying to run an aircraft on a out-of-date version of FlightGear. The planes on the official download page are intended to be used with the latest version of FlightGear. Usage on any older systems may not work.

===freeglut (fgfs): Unable to create direct context rendering for window 'FlightGear' This may hurt performance===
This reports that you do not have proper hardware accelerated 3D (direct rendering) configured.

===Gate ... doesn't seem to have routes associated with it===
A startup location in the [[Interactive Traffic#Ground networks|groundnetwork]] is not (properly) connected to a taxi route. Contact the airport author, or import the network to [[TaxiDraw]] and run the Verify network command to find the corrupted gate.

===glLinkProgram "" Failed===
Update your drivers; they have to support atleast OpenGL 2.0 for FlightGear 2.0 and later.

===loading scenario '...'===
This is not an error. It shows that an [[AI Systems#AI Models|AI scenario]] is loaded.

===Model not found: ...===
This one tells you that FlightGear was unable to find a certain file. The nice thing is that it also tells you excactly what file.

# Check if the file really does not exist at your computer.
# Try to locate the file in which the missing file is referenced. This is likely to be <tt>-set.xml</tt> in the root directory of the loaded [[aircraft]]. Between the <model> tags, the base model file is referenced. This file references to all other models that are displayed with the aircraft.
# Contact the aircraft author with a detailed bug-report, in which you state the excact location of the missing file and (if you found it) the file in which it is referenced.

===Nasal runtime error: nil used in numeric context===
This error is [[Nasal]] triggered by a Nasal file (the console should show what file (and line) and from where it was referenced). The Nasal script tried to do something with a [[Property Tree|property]] with an empty value. A solution is to fill the property before the Nasal is loaded. This can be done by setting the property in an [[aircraft]]'s <tt>-set.xml</tt> file or by adding a [[Nasal scripting language#Listeners and Signals|listener]] to the script.

[[Howto: Contact the developers|Contact the developers]] if this error is shown for a <tt>[[$FG_ROOT]]/Nasal/</tt> script.

===Near camera not rendering===
[[Image:Near_camera_off.png|500px]]

If you screen looks like the image above; make sure you have at least [[OSG]] version 2.7.6.

===No render bin name specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===No render bin number specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===... not a valid win32 application===
This Windows error could have various reasons to pop up. Usually, the file that is causing troubles is mentioned. Re-installing this file might solve the problem.

===OBJECT_SIGN: unsupported glyph `.'===
Check the OBJECT_SIGN lines in the .stg file of the tile that was loaded when this error showed up.

===OpenAL error <AL_INVALID_VALUE>: bind source <alGenSources> Failed to generate audio source.===
This error is probably displayed because of some misdirected audio settings in the [[aircraft]]s setup. Check the -sound.xml file of the aircraft and see if all files refered to really exist. If not, try to contact the author of the plane, so he can fix the problem in the [[FlightGear CVS|CVS]] version or solve the problem yourself and let someone commit the patch.

===OpenAL error (AL_INVALID_VALUE): constructor (alBufferData) Fatal error: Failed to buffer data.===
Disabling sound is a temporarily solution for this problem.

===osgDB ac3d reader: could not find texture...===
See [[#Failed to open file ...|Failed to open file ...]]

===osgDB ac3d reader: detected surface with less than 3 vertices!===
In one of the loaded models a non-existing surface is found. This can be a single line (sometimes used to simulate thin wires) or a fault in the model.

===Program's vertex attrib binding ..., usrAttr...===
Tells you that an effect binded certain attributes to a [[Shaders|shader]].

===QNAN===
(Q)NAN stands for (Quiet) Not A Number, produced by 0/0 or other floating point break downs. There can be various causes for this:
* Using a "flap start" value of 0 in the [[YASim]] [[FDM]]. Use some small value like 0.001 instead.

===Scaling image...===
This means a texture, whether in the scenery on your aircraft or anyone elses (when multiplayer is enabled), is not sized to powers of two. All textures in FlightGear have to be sized to power of two (eg. 16*16, 32*64, 32*1024). As of version 1.9 textures are resized automaticly, but it does slow your computer down, so it's better to resize the noted textures.

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

===The system cannot find the file specified===
If you are running Windows Vista; start by looking in <tt>C:\Users\Owner\AppData\Local\VirtualStore</tt> and seeing if you have a folder called FlightGear in there. If you do, cut-and-paste (merge) that one with <tt>C:\Program Files\Flightgear</tt> and try to launch FlightGear again.

'''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible.

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

===Traffic manager could not find airport===
There is either an airport missing from apt.dat, or there is a wrong ICAO code in a [[Interactive Traffic#Building Traffic Files|traffic file]]. An airport missing from apt.dat could be due to a recent opening.

===Unable to choose requested pixel format===
Error should be solved as of version 1.9. If not, try changing your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] and/or resolution.

===Unable to find airport details for .... in FGTower::Init()===
This error can be surpressed by disabling [[Interactive Traffic|AI Traffic]], via the AI/ATC [[menu]].

The error appears when an airport in <tt>[[$FG_ROOT]]/Airports/apt.dat.gz</tt> cannot be found in <tt>[[$FG_ROOT]]/ATC/default.tower</tt> and <tt>[[$FG_ROOT]]/ATC/default.atis</tt>. Renaming the airports in the apt.dat.gz file ór in both default ATC files will fix the problem.

===Unable to open aircraft directory===
The [[aircraft]] that you are trying to run most likely relies on another aircraft, which you did not install (yet). The error shows what aircraft, so go download that one!
=== Unexpected tag '...' found in YASim aircraft description===
FlightGear found a non-existing tag in the [[FDM]] of the aircraft you are trying to launch. If you have not changed the original aircraft, contact the aircraft author. Else, check the FDM througly for mistakes.

Also, make sure you didn't force a FDM to be loaded.
* '''Commandline:''' <tt>--fdm=...</tt> should be left out.
* '''[[FGRun]]:''' <tt>Advanced > Flight Model</tt> should be set to jsb (which will leave the whole command out of the commandline, so you can use this setting with any FDM).

=== Unknown ... aircraft: ... defaulting to C172 ===
FlightGear is unable to load the forced [[FDM]] (set through <tt>--fdm=...</tt> or via <tt>Advanced > Flight Model</tt> in [[FGRun]]) for this aircraft. FlightGear automatically picks the right FDM for each aircraft, so there is no need to set it manually, unless you know what you are doing. In the Flight Model dialog of FGRun, set the FDM to <tt>jsb</tt>; that is the "auto setting".

===Unknown exception to the main loop. Aborting... Possible cause: No such file or directory===
This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear_Launch_Control#Debugging|log level]] to debug and repeating excactly what you did when the error came up, might provide some more information on what FlightGear was doing when the error occurred.
* Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work.
* Changing the resolution to a smaller one might work as well.

===WARNING: Couldn't convert texture...===
You are trying to run an aircraft not compatible with your FlightGear version. Most of the time, this error appears when you fly an aircraft, textured with .png files on versions older than 1.9. Convert the textures manually to .rgb or upgrade your FlightGear version.

===Warning: Could not find plugin to read objects from file ...===
A library is missing from your computer. Therefore, certain fileformats cannot be read. Try to reinstall/update [[OSG]], as the libraries used by FlightGear should be part of the standard package.

===Warning: Picked up TriangleIntersect===
Reduce your [[FlightGear Launch Control#Debugging|Log Level]] to alert. Or [[Showstoppers|send the fgfs output to /dev/null (unix systems) or 2>nul (Windows)]]. The errors might still be shown, but do not affect the sim anymore.

===Warning: TangentSpaceGenerator: unknown primitive mode 9===
This is an [[OSG]] error, showing up when an effect needs tangent vectors, but polygons are not support. The error itself can be ignored, altough some [[shaders]] may look wrong. Shader developers should try to minimise the use of polygons and use triangles and quads instead.

===YASim SOLUTION FAILURE: Solution failed to converge after 10000 iterations===
Some control in the [[YASim]] [[FDM]] is too weak, according to YASim, to control the aircraft. An effectiveness tag will be required in the FDM to solve this error.

===YASim SOLUTION FAILURE: Zero length fuselage===
There is a problem in the [[FDM]]. A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.

===FGMultiplayerMgr::Open - Failed to bind receive socket===

This means FlightGear was unable to open the listening network socket required by the --multiplay=in option. Frequently this option can be omitted and FlightGear will figure out the necessary parameters automatically.
Common reasons are:
* Address given in the option does not resolve to one of the IP addresses of the local machine. This parameter should only be required if you want to fine-tune the network behavior. Omitting it directs FlightGear to listen on all local interfaces automatically. Example:
--multiplay=in,10,,5001
Notice that you still need the comma.
* The UDP port given in the option (or the default port 5000 if no option given) is already in use. Verify nothing is using the port.

==Errors without known solutions==
Please take a look at the upcoming errors and see if you know a solution to get rid of them. Your additions are greatly appreciated!

===AL Error (fx): Invalid Value at pitch and gain===

===AL Error (sound manager): Invalid Operation at update===

===AL Error (sound manager): Invalid Value at buffer add data No such buffer!===

===Failed to execute command nasal===

===Failed to tie property ... to object methods===
A JSBSim error.

===FGMultiplayMgr::MP_ProcessData - message from ... has invalid length!===

===FGMultiplayMgr::MP_ProcessData: Result too large===

===GPS: malformed route, index=1===

===Mesa 7.3 implementation error: bad texture level in r300UploadSubImage===
http://www.flightgear.org/forums/viewtopic.php?f=2&t=6706&start=0&st=0&sk=t&sd=a

===Nasal runtime error: stack overflow===

===No image file for texture, using white===
A [[Shaders|shader]] error

===No path in /sim/sound/path===

You (or the developer) have/has not specified a proper sound file in the aircraft's -set.xml file.

===OBJECT_SIGN: unexpected } in sign contents===

===OpenAL error (AL_ILLEGAL_COMMAND): set_source_pos===

===OpenAL error (AL_ILLEGAL_COMMAND): set_volume===

===PT_vs_hpt: ran out of layers===
This is issued from the atmosphere implementation in FlightGear's environment system. A comment in the code says: "''should never get here''". Please provide input when this happens: excessive altitudes? Negative altitudes?

===Warning: detected OpenGL error 'invalid value' after RenderBin::draw(,)===
This warning is generated from OSG. Set your environment variable
OSG_NOTIFY_LEVEL=FATAL

===Warning: GraphicsWindowWin32::grabFocus() - Failed grabbing the focus===

It seems that this happens when you have another window open and you are "focusing" (the window is active) on it. FlightGear will try to grab itself infront of the other window.

===WARNING: PUI: Too many live puInterfaces open at once!===
Appears when printing large outputs (very) frequently on the screen.

===Warning: State::drawQuads(0, 154400) too large handle in remapping to ushort glDrawElements===

[[Category:Howto|Get rid of common errors]]

[[fr:Howto: Débarrassez-vous des erreurs les plus fréquentes]]

Howto:Understand console output

2010-11-28T21:57:38Z

Airbird1: /* Warning: GraphicsWindowWin32::grabFocus() - Failed grabbing the focus */ Added explanation

This document lists '''[[FlightGear]] errors''', how to get rid of them and other '''console output'''. If FlightGear quits but does not give you any error, try increasing the [[FlightGear Launch Control#Debugging|Log Level]].

Errors can appear in various locations, but the most common one is the console (a black window), which pops up when you run fgfs.exe.

==Errors with known solutions==
===Airports/.... ... Done===
This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG_SCENERY]]/Airports</tt> directory.

===Base package check failed ... Found version [none] at: ... Please upgrade to version:===
* FlightGear was unable to find the [[$FG_ROOT]] directory. Set it using the <tt>--fg-root=</tt> commandline option.
* When using [[CVS]] with binaries, the data must match the binary. You cannot use data from a different date than the binary's release date.

===condition: comparison without property[1] or value===
A condition (like <tt><less-than></tt> or <tt><equals></tt>) exists, without either:
* a property to check
* a value to check the property against

===Could not find at least one of the following objects for animation:===
This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. If you are not the aircraft's author you can safely ignore such warnings.

===creating 3D noise texture... DONE===
Tells you that a new noise texture is created. It is not an error and can be ignored.

===Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified====
Try changing the [[FlightGear Launch Control#Page Four - Options and Run|BPP]] value of your FlightGear setup. If that does not work, your graphics card is probably not able to run FlightGear 1.9 and higher. Another graphics card, or an older FlightGear version will likely "fix" the problem.

===Error: bind() failed in make_server_socket()===
When using [[Howto: Multiplayer|multiplayer]] or socket input, this usually means you specified an invalid ip address or the port is in use. Note: for multiplayer, you don't need to use the ''--multiplay=in,...'' option at all, FlightGear (since version 1.0) figures out the proper setting automatically. Only use when you know what you are doing.

===Error Building Technique: findAttr: could not find attribute bool===
Make sure that your data and source (or binary) match. They must be from the same date, to provide the best performance.

===Error: connect() failed in make_client_socket() SG_IO_OUT socket creation failed===
Your computer is not connected with the internet.

===Error: RenderTexture requires the following unsupported OpenGL extensions...===
Your graphics card doesn't support some graphics feature that FG requires. Update your drivers, change the BPP value and/or try disabling some of the visual goodies like [[3D Clouds]].

===Failed to find .... in apt.dat.gz===
You need to edit ATC/default.tower and ATC/default.atis. You can open these files with any text editor. Either remove or fix the entries containing your airports ICAO code (like KSFO).

===Failed to locate aircraft carrier = ...===
FlightGear is unable to find a [[Aircraft carrier|carrier]] under the set name. Check your commandline (<tt>--carrier=...</tt>) or the [[FlightGear Launch Control#Page Three - Airport Selection|airport page]] of the launcher.

===Failed to open file ...===
Check if the file exists on your system. If the missing file is a scenery object; be sure you have the latest [http://scenemodels.flightgear.org/download/SharedModels.tgz Shared Models] from the [[FlightGear Scenery Database]].

===Fatal error: mismatched tag ...===
In some .xml file, an opening tag (like <tt><sim></tt>) does not match its closing tag (like <tt></sim></tt>). This error is hard to track down, best method is to comment (place code between <nowiki></nowiki>) most of the aircraft. Then uncomment code one by one, until the error appears again.

===Fatal error: name must begin with alpha or '_'===
This error comes up when a property should be formed of which the name does not start with a letter of the alphabet or _. If this error only happens with certain planes, contact their authors.

===Fatal error: unclosed token===
A token (<nowiki></nowiki>) has been started, but not closes. Add <nowiki>--></nowiki> at the correct line.

===FGMultiplayMgr::MP_ProcessData: No such file or directory===
This is telling you that there's someone online on the multiplayerserver, using a plane that you do not have installed on your own system. In order to remove the error (and see the other plane) you have to install the plane that the other pilot is using.

===FGMultiplayMgr - No receiver port, Multiplayermode disabled===
FlightGear [[Howto: Multiplayer|multiplayer]] has not been set.

===FGPropertyManager::GetNode() No node found for ... In component: ... unknown property ... referenced. Aborting===
FlightGear found a reference in the [[FDM]] to a non-existing property.

===FGPropertyManager::GetNode() No node found for ... The property ... is undefined.===
FlightGear found a reference in the [[FDM]] to a non-existing property. Keep in mind that JSBSim reads the FDM from top to bottom. Properties should always be created before they are needed somewhere.

===Fgtzfile_read(): : Invalid argument Fatal error: Timezone reading failed===
This one is caused by wrong line ending in a timezone file. Solution might be to download the Timezone/time.tab file manually from [http://gitorious.org/fg/fgdata/blobs/raw/master/Timezone/zone.tab Gitorious] (Right mouseclick > Save target as) and overwrite the file in <tt>[[$FG_ROOT]]/Timezone/time.tab</tt> with it.

===Found unexpected subsystem: system exiting. JSBSim failed to load aircraft and/or engine model===
You are probably trying to run an aircraft on a out-of-date version of FlightGear. The planes on the official download page are intended to be used with the latest version of FlightGear. Usage on any older systems may not work.

===freeglut (fgfs): Unable to create direct context rendering for window 'FlightGear' This may hurt performance===
This reports that you do not have proper hardware accelerated 3D (direct rendering) configured.

===Gate ... doesn't seem to have routes associated with it===
A startup location in the [[Interactive Traffic#Ground networks|groundnetwork]] is not (properly) connected to a taxi route. Contact the airport author, or import the network to [[TaxiDraw]] and run the Verify network command to find the corrupted gate.

===glLinkProgram "" Failed===
Update your drivers; they have to support atleast OpenGL 2.0 for FlightGear 2.0 and later.

===loading scenario '...'===
This is not an error. It shows that an [[AI Systems#AI Models|AI scenario]] is loaded.

===Model not found: ...===
This one tells you that FlightGear was unable to find a certain file. The nice thing is that it also tells you excactly what file.

# Check if the file really does not exist at your computer.
# Try to locate the file in which the missing file is referenced. This is likely to be <tt>-set.xml</tt> in the root directory of the loaded [[aircraft]]. Between the <model> tags, the base model file is referenced. This file references to all other models that are displayed with the aircraft.
# Contact the aircraft author with a detailed bug-report, in which you state the excact location of the missing file and (if you found it) the file in which it is referenced.

===Nasal runtime error: nil used in numeric context===
This error is [[Nasal]] triggered by a Nasal file (the console should show what file (and line) and from where it was referenced). The Nasal script tried to do something with a [[Property Tree|property]] with an empty value. A solution is to fill the property before the Nasal is loaded. This can be done by setting the property in an [[aircraft]]'s <tt>-set.xml</tt> file or by adding a [[Nasal scripting language#Listeners and Signals|listener]] to the script.

[[Howto: Contact the developers|Contact the developers]] if this error is shown for a <tt>[[$FG_ROOT]]/Nasal/</tt> script.

===Near camera not rendering===
[[Image:Near_camera_off.png|500px]]

If you screen looks like the image above; make sure you have at least [[OSG]] version 2.7.6.

===No render bin name specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===No render bin number specified in render bin section===
Update [[SimGear]] (or binary) and your data directory.

===... not a valid win32 application===
This Windows error could have various reasons to pop up. Usually, the file that is causing troubles is mentioned. Re-installing this file might solve the problem.

===OBJECT_SIGN: unsupported glyph `.'===
Check the OBJECT_SIGN lines in the .stg file of the tile that was loaded when this error showed up.

===OpenAL error <AL_INVALID_VALUE>: bind source <alGenSources> Failed to generate audio source.===
This error is probably displayed because of some misdirected audio settings in the [[aircraft]]s setup. Check the -sound.xml file of the aircraft and see if all files refered to really exist. If not, try to contact the author of the plane, so he can fix the problem in the [[FlightGear CVS|CVS]] version or solve the problem yourself and let someone commit the patch.

===OpenAL error (AL_INVALID_VALUE): constructor (alBufferData) Fatal error: Failed to buffer data.===
Disabling sound is a temporarily solution for this problem.

===osgDB ac3d reader: could not find texture...===
See [[#Failed to open file ...|Failed to open file ...]]

===osgDB ac3d reader: detected surface with less than 3 vertices!===
In one of the loaded models a non-existing surface is found. This can be a single line (sometimes used to simulate thin wires) or a fault in the model.

===Program's vertex attrib binding ..., usrAttr...===
Tells you that an effect binded certain attributes to a [[Shaders|shader]].

===QNAN===
(Q)NAN stands for (Quiet) Not A Number, produced by 0/0 or other floating point break downs. There can be various causes for this:
* Using a "flap start" value of 0 in the [[YASim]] [[FDM]]. Use some small value like 0.001 instead.

===Scaling image...===
This means a texture, whether in the scenery on your aircraft or anyone elses (when multiplayer is enabled), is not sized to powers of two. All textures in FlightGear have to be sized to power of two (eg. 16*16, 32*64, 32*1024). As of version 1.9 textures are resized automaticly, but it does slow your computer down, so it's better to resize the noted textures.

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

===The system cannot find the file specified===
If you are running Windows Vista; start by looking in <tt>C:\Users\Owner\AppData\Local\VirtualStore</tt> and seeing if you have a folder called FlightGear in there. If you do, cut-and-paste (merge) that one with <tt>C:\Program Files\Flightgear</tt> and try to launch FlightGear again.

'''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible.

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

===Traffic manager could not find airport===
There is either an airport missing from apt.dat, or there is a wrong ICAO code in a [[Interactive Traffic#Building Traffic Files|traffic file]]. An airport missing from apt.dat could be due to a recent opening.

===Unable to choose requested pixel format===
Error should be solved as of version 1.9. If not, try changing your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] and/or resolution.

===Unable to find airport details for .... in FGTower::Init()===
This error can be surpressed by disabling [[Interactive Traffic|AI Traffic]], via the AI/ATC [[menu]].

The error appears when an airport in <tt>[[$FG_ROOT]]/Airports/apt.dat.gz</tt> cannot be found in <tt>[[$FG_ROOT]]/ATC/default.tower</tt> and <tt>[[$FG_ROOT]]/ATC/default.atis</tt>. Renaming the airports in the apt.dat.gz file ór in both default ATC files will fix the problem.

===Unable to open aircraft directory===
The [[aircraft]] that you are trying to run most likely relies on another aircraft, which you did not install (yet). The error shows what aircraft, so go download that one!
=== Unexpected tag '...' found in YASim aircraft description===
FlightGear found a non-existing tag in the [[FDM]] of the aircraft you are trying to launch. If you have not changed the original aircraft, contact the aircraft author. Else, check the FDM througly for mistakes.

Also, make sure you didn't force a FDM to be loaded.
* '''Commandline:''' <tt>--fdm=...</tt> should be left out.
* '''[[FGRun]]:''' <tt>Advanced > Flight Model</tt> should be set to jsb (which will leave the whole command out of the commandline, so you can use this setting with any FDM).

=== Unknown ... aircraft: ... defaulting to C172 ===
FlightGear is unable to load the forced [[FDM]] (set through <tt>--fdm=...</tt> or via <tt>Advanced > Flight Model</tt> in [[FGRun]]) for this aircraft. FlightGear automatically picks the right FDM for each aircraft, so there is no need to set it manually, unless you know what you are doing. In the Flight Model dialog of FGRun, set the FDM to <tt>jsb</tt>; that is the "auto setting".

===Unknown exception to the main loop. Aborting... Possible cause: No such file or directory===
This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear_Launch_Control#Debugging|log level]] to debug and repeating excactly what you did when the error came up, might provide some more information on what FlightGear was doing when the error occurred.
* Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work.
* Changing the resolution to a smaller one might work as well.

===WARNING: Couldn't convert texture...===
You are trying to run an aircraft not compatible with your FlightGear version. Most of the time, this error appears when you fly an aircraft, textured with .png files on versions older than 1.9. Convert the textures manually to .rgb or upgrade your FlightGear version.

===Warning: Could not find plugin to read objects from file ...===
A library is missing from your computer. Therefore, certain fileformats cannot be read. Try to reinstall/update [[OSG]], as the libraries used by FlightGear should be part of the standard package.

===Warning: Picked up TriangleIntersect===
Reduce your [[FlightGear Launch Control#Debugging|Log Level]] to alert. Or [[Showstoppers|send the fgfs output to /dev/null (unix systems) or 2>nul (Windows)]]. The errors might still be shown, but do not affect the sim anymore.

===Warning: TangentSpaceGenerator: unknown primitive mode 9===
This is an [[OSG]] error, showing up when an effect needs tangent vectors, but polygons are not support. The error itself can be ignored, altough some [[shaders]] may look wrong. Shader developers should try to minimise the use of polygons and use triangles and quads instead.

===YASim SOLUTION FAILURE: Solution failed to converge after 10000 iterations===
Some control in the [[YASim]] [[FDM]] is too weak, according to YASim, to control the aircraft. An effectiveness tag will be required in the FDM to solve this error.

===YASim SOLUTION FAILURE: Zero length fuselage===
There is a problem in the [[FDM]]. A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.

===FGMultiplayerMgr::Open - Failed to bind receive socket===

This means FlightGear was unable to open the listening network socket required by the --multiplay=in option. Frequently this option can be omitted and FlightGear will figure out the necessary parameters automatically.
Common reasons are:
* Address given in the option does not resolve to one of the IP addresses of the local machine. This parameter should only be required if you want to fine-tune the network behavior. Omitting it directs FlightGear to listen on all local interfaces automatically. Example:
--multiplay=in,10,,5001
Notice that you still need the comma.
* The UDP port given in the option (or the default port 5000 if no option given) is already in use. Verify nothing is using the port.

==Errors without known solutions==
Please take a look at the upcoming errors and see if you know a solution to get rid of them. Your additions are greatly appreciated!

===AL Error (fx): Invalid Value at pitch and gain===

===AL Error (sound manager): Invalid Operation at update===

===AL Error (sound manager): Invalid Value at buffer add data No such buffer!===

===Failed to execute command nasal===

===Failed to tie property ... to object methods===
A JSBSim error.

===FGMultiplayMgr::MP_ProcessData - message from ... has invalid length!===

===FGMultiplayMgr::MP_ProcessData: Result too large===

===GPS: malformed route, index=1===

===Mesa 7.3 implementation error: bad texture level in r300UploadSubImage===
http://www.flightgear.org/forums/viewtopic.php?f=2&t=6706&start=0&st=0&sk=t&sd=a

===Nasal runtime error: stack overflow===

===No image file for texture, using white===
A [[Shaders|shader]] error

===No path in /sim/sound/path===

===OBJECT_SIGN: unexpected } in sign contents===

===OpenAL error (AL_ILLEGAL_COMMAND): set_source_pos===

===OpenAL error (AL_ILLEGAL_COMMAND): set_volume===

===PT_vs_hpt: ran out of layers===
This is issued from the atmosphere implementation in FlightGear's environment system. A comment in the code says: "''should never get here''". Please provide input when this happens: excessive altitudes? Negative altitudes?

===Warning: detected OpenGL error 'invalid value' after RenderBin::draw(,)===
This warning is generated from OSG. Set your environment variable
OSG_NOTIFY_LEVEL=FATAL

===Warning: GraphicsWindowWin32::grabFocus() - Failed grabbing the focus===

It seems that this happens when you have another window open and you are "focusing" (the window is active) on it. FlightGear will try to grab itself infront of the other window.

===WARNING: PUI: Too many live puInterfaces open at once!===
Appears when printing large outputs (very) frequently on the screen.

===Warning: State::drawQuads(0, 154400) too large handle in remapping to ushort glDrawElements===

[[Category:Howto|Get rid of common errors]]

[[fr:Howto: Débarrassez-vous des erreurs les plus fréquentes]]

Airbus A350 XWB

2010-11-07T20:21:23Z

Airbird1: Added Airbus box

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

{{infobox Aircraft
|image =A350.png
|alt =A350-1000 in Sketchup
|name =Airbus A350-1000
|type =Airliner
|fdm =JSBSim
|status =Under development
|authors =EA-7201
|fgname =A350-1000
}}

The '''Airbus A350''' is a long-range, mid-size, wide-body family of airliners currently under development by European manufacturing group [[:Category:Airbus|Airbus]]. The A350 will be the first Airbus with fuselage and wing structures made primarily of carbon fiber-reinforced plastic. The A350 is designed to compete with the [[Boeing 777]] and the [[Boeing 787]]. Airbus claims that it will be more fuel-efficient, with up to 8% lower operating cost than the Boeing 787. It is scheduled to enter into airline service in 2013.

== Work stage ==

=== Completed ===
* Engines
* XMLs
* Model

=== In progress ===
* Liveries

=== To do ===
* Animations

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]
{{Airbus}}

Virtual airlines

2010-11-06T01:58:18Z

Airbird1:

A '''virtual airline''' (VA) is a dedicated hobby organization that uses flight simulation to model the operations of an airline. Virtual airlines generally have a presence on the internet, similar to a real airline. There are over 100 virtual airlines of significance currently active in the internet (supporting a number of flightsims), with thousands of participants involved at any one time each using different simulator platforms.

==A note==
There has been a rapidly expanding number of VAs in Flightgear, and there is not enough people to support this bugeoning explosion of VAs. So think twice about creating a VA, because we're running out of pilots.

==Purpose==
Virtual airlines were started to give a sense of purpose to activities conducted within a flight simulator. This basic premise has evolved over time, along with available technology, to provide increasing levels of immersion but always with the same core purpose. When combined with increasingly powerful personal computers, advancing flight simulation software, and communications networks, virtual airlines are often able to provide compelling, realistic, experiences similar to operations inside a real airline. Virtual airlines also provide an avenue for members to gain access to additional content, such as aircraft and scenery, for use with their simulator. The appeal varies; for younger members, virtual airlines provide a sandbox environment where they can experience the corporate environment of commercial business in the airline industry, without the risk of financial loss. These organizations also provide an outlet for those who are interested in aviation but unable to fly themselves in real life due to financial, health, or other reasons.
Most of all, its one step closer to enthusiasts feeling more involved in an airline environment and share their interests with others.
Virtual Airlines also benefit the flight simulator community by providing valuable services such as ATC, events, and general help and knowledge.

==Common elements==
There are several elements that are common across many virtual airlines:
* A website as the focal point of the community
* Internet forum where discussion and social interaction can occur
* Customized livery that users can download together with aircraft and install in their flight simulator
* Route schedules for members to fly in their simulators
* Multiplayer events, often on a game network such as VATSIM or IVAO
* Less common elements include:
* An Online database for recording and reporting flights and membership statistics
* Dedicated game server hosting to provide private areas for members to complete flights
* Award, rank and recognition systems
* Voice over Internet Protocol servers for members to communicate freely by voice

==Current Flightgear Virtual Airlines==
Currently, some number of virtual airlines exist, with airlines made of various experiences, fleets and operations. Here is a list of some of the known virtual airlines to have existed:

* Air H5
* Trans Pacific Express
* [[Ares Virtual Airlines]]
* [[Atlas Virtual Airlines]]
* Delta Virtual Airlines
* [[Star Alliance]]
* [http://transgear.treborlogic.com TransGear Airways]
*[[BRT Virtual Airlines]]

===Current Alliances===
Alliances point to groups of airlines working with each other in joint operations. Currently, the following are active:
* [[Star Alliance]]
* Transgear Airways and Atlas (considered "sister VA's" and work in symbiosis)

===Current Flightgear Flying Clubs===
* [http://flightgearfans.wordpress.com/ FlightGear Flying Club]

==Former Virtual Airlines==
Before the merger of most virtual airlines into Atlas and gradual declines of airlines following that event, several independent virtual airlines were active. These airlines, as well as airlines proposed but never actually created include the following:
[[Image:virtualairlines.jpg|thumb|430px|Logo of most virtual airlines as of February 2010.]]

===Airlines Merged into Atlas Virtual===
* [[Japan Pacific Airlines]]
* Skynet International Airlines

===Defunct Airlines===
* AirLink
* Air San Francisco
* Americair
* Coastal Air Systems
* Detra Virtual Airlines
* Euroair (Aurelen Virtual)
* [[Europe Airlines]]
* Gisi Airlines

===Proposed Airlines===
* Sandy Oceania Airlines
* Triangle Airlines

==Controversies==
===Copyright Issues===
When a virtual airline is created in the image of a real world airline legal issues can arise out of copyright violations. In 2003, a real world airline, Qantas Airways Ltd., announced a new low-cost carrier by the name of Jetstar Airways. However, a virtual airline named Jetstar International Airlines already existed, complete with a web site. As part of their startup promotion, Qantas sold 100,000 airline tickets at a discount price, and the virtual airline's web site was swamped with would-be customers, job-seekers, and prospective vendors. The virtual airline sued Qantas, claiming that Qantas stole the virtual airline's livery and trademark.
If you wish to create a virtual airline- Which Flightgear would be eager for you to do, Please do not base it on real life airlines to save copyright issues!

===Association with terrorism===
Claims have been made of the use of both flight simulators and virtual airlines as training devices for terrorist activities, although to date no conclusive link has ever been provided to indicate a situation where a virtual airline has provided flight simulation training to anyone involved in a terrorist activity.
Jermaine Lindsay, one of the four 7 July 2005 London bombings, may have used flight simulators to practice flying an airliner, with an accusation that he was registered with a virtual airline. A person of the same name listed his nearest major airport as Heathrow and clocked up 30 hours in two months with SimAirline.net. The website later denied the member's linking with the bombing, and indicated it was working with the Metropolitan Police to establish whether its former member was the bomber. The website stated that it provides information about airlines and free add-on software for Microsoft Flight Simulator and does not provide flight instruction to its members.
The 9/11 Commission in the US concluded in 2004 that those responsible for flying the planes into World Trade Center and Pentagon had used PC-based flight simulators for training. Despite the initial concerns of the involvement of virtual airlines in these terrorist activities, largely little has come from these claims to date and no changes have been noted as occurring in their operation as a result.

Virtual airlines

2010-11-06T01:44:52Z

Airbird1: /* Current Flightgear Virtual Airlines */ Added Trans Pacific Express

A '''virtual airline''' (VA) is a dedicated hobby organization that uses flight simulation to model the operations of an airline. Virtual airlines generally have a presence on the internet, similar to a real airline. There are over 100 virtual airlines of significance currently active in the internet (supporting a number of flightsims), with thousands of participants involved at any one time each using different simulator platforms.

==Purpose==
Virtual airlines were started to give a sense of purpose to activities conducted within a flight simulator. This basic premise has evolved over time, along with available technology, to provide increasing levels of immersion but always with the same core purpose. When combined with increasingly powerful personal computers, advancing flight simulation software, and communications networks, virtual airlines are often able to provide compelling, realistic, experiences similar to operations inside a real airline. Virtual airlines also provide an avenue for members to gain access to additional content, such as aircraft and scenery, for use with their simulator. The appeal varies; for younger members, virtual airlines provide a sandbox environment where they can experience the corporate environment of commercial business in the airline industry, without the risk of financial loss. These organizations also provide an outlet for those who are interested in aviation but unable to fly themselves in real life due to financial, health, or other reasons.
Most of all, its one step closer to enthusiasts feeling more involved in an airline environment and share their interests with others.
Virtual Airlines also benefit the flight simulator community by providing valuable services such as ATC, events, and general help and knowledge.

==Common elements==
There are several elements that are common across many virtual airlines:
* A website as the focal point of the community
* Internet forum where discussion and social interaction can occur
* Customized livery that users can download together with aircraft and install in their flight simulator
* Route schedules for members to fly in their simulators
* Multiplayer events, often on a game network such as VATSIM or IVAO
* Less common elements include:
* An Online database for recording and reporting flights and membership statistics
* Dedicated game server hosting to provide private areas for members to complete flights
* Award, rank and recognition systems
* Voice over Internet Protocol servers for members to communicate freely by voice

==Current Flightgear Virtual Airlines==
Currently, some number of virtual airlines exist, with airlines made of various experiences, fleets and operations. Here is a list of some of the known virtual airlines to have existed:

* Air H5
* Trans Pacific Express
* [[Ares Virtual Airlines]]
* [[Atlas Virtual Airlines]]
* Delta Virtual Airlines
* [[Star Alliance]]
* [http://transgear.treborlogic.com TransGear Airways]
*[[BRT Virtual Airlines]]

===Current Alliances===
Alliances point to groups of airlines working with each other in joint operations. Currently, the following are active:
* [[Star Alliance]]
* Transgear Airways and Atlas (considered "sister VA's" and work in symbiosis)

===Current Flightgear Flying Clubs===
* [http://flightgearfans.wordpress.com/ FlightGear Flying Club]

==Former Virtual Airlines==
Before the merger of most virtual airlines into Atlas and gradual declines of airlines following that event, several independent virtual airlines were active. These airlines, as well as airlines proposed but never actually created include the following:
[[Image:virtualairlines.jpg|thumb|430px|Logo of most virtual airlines as of February 2010.]]

===Airlines Merged into Atlas Virtual===
* [[Japan Pacific Airlines]]
* Skynet International Airlines

===Defunct Airlines===
* AirLink
* Air San Francisco
* Americair
* Coastal Air Systems
* Detra Virtual Airlines
* Euroair (Aurelen Virtual)
* [[Europe Airlines]]
* Gisi Airlines

===Proposed Airlines===
* Sandy Oceania Airlines
* Triangle Airlines

==Controversies==
===Copyright Issues===
When a virtual airline is created in the image of a real world airline legal issues can arise out of copyright violations. In 2003, a real world airline, Qantas Airways Ltd., announced a new low-cost carrier by the name of Jetstar Airways. However, a virtual airline named Jetstar International Airlines already existed, complete with a web site. As part of their startup promotion, Qantas sold 100,000 airline tickets at a discount price, and the virtual airline's web site was swamped with would-be customers, job-seekers, and prospective vendors. The virtual airline sued Qantas, claiming that Qantas stole the virtual airline's livery and trademark.
If you wish to create a virtual airline- Which Flightgear would be eager for you to do, Please do not base it on real life airlines to save copyright issues!

===Association with terrorism===
Claims have been made of the use of both flight simulators and virtual airlines as training devices for terrorist activities, although to date no conclusive link has ever been provided to indicate a situation where a virtual airline has provided flight simulation training to anyone involved in a terrorist activity.
Jermaine Lindsay, one of the four 7 July 2005 London bombings, may have used flight simulators to practice flying an airliner, with an accusation that he was registered with a virtual airline. A person of the same name listed his nearest major airport as Heathrow and clocked up 30 hours in two months with SimAirline.net. The website later denied the member's linking with the bombing, and indicated it was working with the Metropolitan Police to establish whether its former member was the bomber. The website stated that it provides information about airlines and free add-on software for Microsoft Flight Simulator and does not provide flight instruction to its members.
The 9/11 Commission in the US concluded in 2004 that those responsible for flying the planes into World Trade Center and Pentagon had used PC-based flight simulators for training. Despite the initial concerns of the involvement of virtual airlines in these terrorist activities, largely little has come from these claims to date and no changes have been noted as occurring in their operation as a result.

Aircraft carrier

2010-11-06T01:33:24Z

Airbird1: Added USS Clemenceau and USS Carl Vinson

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

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

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

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

S-Turns

2010-11-06T01:30:30Z

Airbird1: ADDED CLEANUP AND STUB

{{cleanup}}
{{stub}}

OBJECTIVE: To develop the pilot's ability to compensate for drift during turns, orient the flightpath with ground references, and divide the pilot's attention

ELEMENTS:

A. How to select a suitable altitude.
B. How to select a suitable ground reference line with suitable emergency landing areas.
C. Orientation, division of attention, and planning.
D. Configuration and airspeed prior to entry.
E. Entry technique.
F. Wind drifts correction.
G. Tracking of semicircles of equal radii on either side of the selected ground reference line.
H. How to maintain desired altitude and airspeed.
I. Turn reversal over the ground reference line.
J. Coordination of flight controls.

ASSOCIATED MANEUVERS:

SCHEDULE: Pre-flight instruction: 10 Minutes
Travel to training area: 10 Minutes
Instructor Demonstration: 10 Minutes
Student Practice: 20 Minutes
Return from practice area: 10 minutes
Post-flight Review: 10 Minutes
Total Time: 1:10

EQUIPMENT: Functional aircraft.

INSTRUCTOR’S ACTIONS: A. Conduct preflight training on the elements of S Turns.
B. Demonstrate S Turns
F. Conduct post flight briefing.

STUDENT’S ACTIONS: A. Ask questions, review homework.
B. Perform preflight.
C. Observe demonstrations.
D. Perform IAW PTS.

COMPLETION STANDARDS: Student performs S Turns IAW the PTS.

COMMON ERRORS: A. Faulty entry technique.
B. Poor planning, orientation, or division of attention.
C. Uncoordinated flight control application.
D. Improper correction for wind drift.
E. A non-symmetrical ground track.
F. Failure to maintain selected altitude or airspeed.
G. Selection of a ground reference line where this is no suitable emergency landing area within gliding distance.

Introduction: Every time we turn the airplane we make adjustments for the wind. This is especially true for flying in the traffic pattern. In the pattern we want to maintain the same relative distance to the runway until we turn final. S-turns show us the effect that wind has on an airplane and how we compensate for that while in a turn. Basically we will do this about 1000 feet agl. We will use a road or some other clearly identifiable straight line on the ground. We will fly across the road with the wind, then turn back toward the road, level of in time to cross the road and then turn again towards the road. This makes an “S” pattern across the road. The object here is to maintain perfect half circles on either side of the road and to be wings level ONLY long enough to cross the road. You maintain your relative position by adjusting your angle of bank and hence your rate of turn. You need to keep your altitude and airspeed where you start the maneuver.

A. Lesson Requirements:

1. Task: Perform a S-turn.

2. Condition: Given a functional aircraft.

3. Standard: IAW the PTS.

a. Exhibits knowledge of the elements related to S-turns.

b. Determines the wind direction and speed.

c. Selects the reference line with an emergency landing area within gliding distance.

d. Plans the maneuver so as to enter at 600 to 1,000 feet (180 to 300 meters) AGL, perpendicular to the selected reference line, downwind, with the first series of turns to the left.

e. Applies adequate wind-drift correction to track a constant radius half-circle on each side of the selected reference line.

f. Divides attention between airplane control and the ground track and maintains coordinated flight.

g. Reverses course, as directed by the examiner, and exits at the point of entry at the same altitude and airspeed at which the maneuver was started.

h. Maintains altitude +- 100 feet (30 m) and airspeed +- 10 knots.

B. ELO 1: Understand the effects of wind on a flying airplane.

1. The air is more like the ocean than a solid mass. As the wind blows it will tend to push an airplane in the direction of airflow. This is just like an boat in a river as it flows in the direction of the stream. Pilots compensate for this by adjusting the crab angle in straight slight, and by adjusting the angle of bank in turns.

2. How do winds affect groundspeed? Moving downwind (with the wind) causes the airplane to have an increase in groundspeed. Moving upwind (against the wind) causes the airplane to have a decrease in groundspeed. In both cases the airspeed indicator may read the same.

3. How do winds affect the angle of bank and rate of turn? When traveling on the downwind side of the turn the airplane tends to increase speed and a greater rate of turn must be used to compensate for the increased airspeed. On the upwind side of the turn, the bank will be shallower because the airplane is moving slower.

4. Student Check:

What portion of the S-turn will have a steeper turn? _______
Where do you enter the S-turn relative to the wind? ______

C. ELO 2: Identify common errors in the S-turn.

1. Faulty entry technique.

2. Poor planning, orientation, or division of attention.

3. Uncoordinated flight control application.

4. Improper correction for wind drift.

5. A non-symmetrical ground track.

6. Failure to maintain selected altitude or airspeed.

7. Selection of a ground reference line where this is no suitable emergency landing area within gliding distance.

8. Student Check:

i. What is Vx on this aircraft? ________
ii. What is Vy on this aircraft? ________

D. ELO 3: Perform a S-turn.

1. Pick an appropriate entry altitude (700-1000 ft agl works well). NO LOWER than 500 feet agl.

2. Pick your reference line.

3. Enter the maneuver WITH the wind and perpendicular to the line. Once you cross the reference line, start a 180 degree turn.

4. Maintain the turn until you come about 180 degrees. This should be just as you are about to cross your reference line.

5. Once you cross the reference line begin a turn in the other direction to complete the S.

6. Maintain the turn until you come about 180 degrees. This should be just as you are about to cross your reference line.

7. Continue the maneuver until told to stop.

Category:Air Traffic Control

2010-11-06T01:27:28Z

Airbird1: Added ATC-navbar

{{ATC-navbar}}

This category covers Air Traffic Control, more commonly known as "ATC".

ATC phraseology

2010-11-06T01:26:33Z

Airbird1:

{{ATC-navbar}}
This page lists some common phraseologies used in the communication between pilots and [[ATC]].

For a detailed tutorial in ATCing, please take a look at the [[ATC Tutorial]].

===Affirmative===
*Abbreviation: aff
Yes.

===Call===
Contact me. Usually ATC asks you to make contact after you've done something or you are ready to do something.

===Cleared for takeoff runway 28L===
You are cleared for takeoff from runway 28L. Only this sentence (and really nothing else) gives you clearence for takeoff from the said runway.

If the word immediate is added (eg. Cleared for immediate takeoff runway 28L), you are only cleared for takeoff if you are able to do so within a very short time. Usually traffic is coming in on the same runway, so do not enter the runway if you are not ready for takeoff in this case.

===Cleared to land runway 28R===
You are cleared to land at runway 28L. Only this sentence (and really nothing else) gives you clearence to land at the said runway. Always make a visual check to see if the runway is really clear!

===Climb and maintain 8000 ft===
*Abbreviation: c/m.
Climb to 8000 ft and hold that altitude until further instructions are given.

===Descend and maintain 8000 ft===
*Abbreviation: d/m.
Descend to 8000 ft and hold that altitude until further instructions are given.

===Hold short===
*Abbreviation: h/s.
You are cleared to taxi to a certain location, but you should wait at the designated point. This can be a runway entrance, or a taxiway crossing. As soon as you reached the designated point, you inform the ATC that you are "Holding short".

===Initiate missed approach===
For some reason ATC wants you to abort the landing; there might be traffic on the runway. Immediately abort your landing and follow the missed approach procedure appropriate to your aircraft. Usually the ATC will give some instructions like altitude and heading. As you have to redo your approach, you are requested to contact approach again.

===Line up and wait===
Enter the runway, position yourself in the center and await further clearance.

Note: The phrase "(taxi into) position and hold" is no longer used.

===Negative===
*Abbreviation: neg
No.

===One orbit to the left===
Make a circle to the left and then continue on the original heading. ATC may tell you to do so if a little more spacing between you and the aircraft in front of you is required.

===Report established===
Tell the ATC once you are established.

===Roger===
*Abbreviation: rgr
I received your information.

===Say again===
Repeat your last message.

===Will Comply===
*Abbreviation: wilco

[[Category:Air Traffic Control]]

__NOTOC__
__NOEDITSECTION__

Air traffic control

2010-11-06T01:25:24Z

Airbird1: Linked to Category:Air Traffic Control

{{ATC-navbar}}
'''Air traffic control''' ('''ATC''') is a service mostly provided by ground-based controllers who direct [[aircraft]] on the ground and in the air. The primary purpose of ATC systems worldwide is to separate aircraft to prevent collisions, to organize and expedite the flow of traffic, and to provide information and other support for pilots when able. In some countries, ATC may also play a security or defense role (as in the United States), or actually be run entirely by the military (as in Brazil).

==FlightGear and ATC==
There is the limited possibility of ATC with [[FlightGear]] [[v0.9.10]] and [[v1.0.0]].

===Frequencies===
'''<tt>Menu > ATC/ AI</tt>''' 
Set the right frequencies and around your choosen airport you can read (or here with festival) the ATC-Messages for [[AI-traffic]]. For that you have to check under options "enable ATC". If you check "enable AI Traffic" too, you will have some AI traffic (c172) around the airports.

===ATC Chatter===
'''<tt>Menu > Sound Configuration</tt>''' 
Check "ATC Chatter" to hear some random records of real-ATC. For the right feeling! ;-)

===Frequency===
Set the right frequency to COM1 with '-key you will have the possibility in some areas to send messages

===ATIS (Automatic Terminal Information Service)===
Set the right frequency of the ATIS to COM 1 and you will hear the ATIS for the choosen Airport (unfortunately a little bit low)

===Multiplayer===
Sometimes someone plays the "Tower" at the [[Multiplayer Howto|multiplayer]] server by using the [[ATC-aircraft]]. You can communicate with <tt>Menu > View > Chat</tt> or by using [[Chat Menu|predefined messages]] with <tt>Menu > View > Chat Menu</tt>. If you want to talk, instead of typing, you can use [[FGCOM]] too! But be aware not all controllers have FGCOM.

'''There is not as of yet an artificial-interactive ATC implemented, so the ATC-system in [[FlightGear]] is still limited.'''

==Related content==
* [[ATC phraseology]] lists common phraseology and their meanings.
* [[ATC Tutorial]] to find out how ATC should be used.
* [[Howto: Be a controller]] to learn how to set yourself up as an ATC in FlightGear.
* [http://www.faa.gov/air_traffic/publications/atpubs/aim/ FAA's Aeronautical Information Manual]
[[Category:Menubar]]
[[Category:FlightGear feature]]
[[Category:Air Traffic Control]]

Category:Air Traffic Control

2010-11-06T01:23:51Z

Airbird1: New Category:Air Traffic Control

This category covers Air Traffic Control, more commonly known as "ATC".

ATC-aircraft

2010-11-06T01:22:24Z

Airbird1: /* Links */ The only link in the section "Links" is broken. Deleted section "links"

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

Currently two version of ATC-aircraft are available.

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

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

==Todo/Bugs==
* The radar screen is oversized on some screen sizes. It should be automatically resized for any window size.
* The screen showing the ATC view is very small when viewed with radar. The radar screen should be resized by the user if possible.
* There are some bugs when using normal [[Howto: Multiplayer#Multiplayer Chat|MP Chat]]. You can't then use it again (FG has to be restarted to fix the bug) and you have to use the ATC Chat box at the bottom.

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

[[Category:Aircraft]]
[[Category:Air_Traffic_Control]]

ATC tutorial

2010-11-06T01:12:45Z

Airbird1: /* _GND (Ground) */ You don't NEED a Ground Sector File.

{{ATC-navbar}}
{{Main article|Air Traffic Control}}

[[Air Traffic Control]] is an agreed procedure and process which keeps the [[aircraft]] separated to ensure that they don't crash into each other or are affected by turbulence when passing through the same air space. The separation of planes taking off or landing at airports is three minutes. This allows the air to settle again. Pilots have used an analogy of calling the atmosphere soup as air and liquid has similar properties.

In order to be able to effectively and reliably communicate, ATC and pilots agree on a set of keywords and jargon. This may vary between regions and the like. English is the agreed language for internaltional flights. 

==Lesson 1==
{| class="prettytable"
! align="center" bgcolor="#EFEFEF" | Position Suffix
! align="center" bgcolor="#EFEFEF" | Name
! align="center" bgcolor="#EFEFEF" | Description
|-
| xxxx_GND
|Ground Controller
|Controls the movement of aircraft on the ground at an airport, however only the taxiways and bays... not the active runways. Whenever a plane needs to cross an active runway, it has to call the tower.
|-
! bgcolor="#EFEFEF" align="left" |xxxx_TWR
! bgcolor="#EFEFEF" align="left" |Tower Controller
! bgcolor="#EFEFEF" align="left" |'Owns' the runways and the airspace up to 10 NM (nautical miles) from the airport. Clears planes for takeoff and landing.
|-
|xxxx_APP
|Approach Controller
|Controls the airspace up to 30NM away from the airport, up to 18,000 ft (usually). Handles all aircraft leaving or arriving at an airport, until they are established on the ILS (then gives the plane to TWR) or are leaving their airspace to continue flight (then hands off to CTR)
|-
! bgcolor="#EFEFEF" align="left" |xxxx_DEP
! bgcolor="#EFEFEF" align="left" |Departure Controller
! bgcolor="#EFEFEF" align="left" |An position rarely used except at busy airports in the real world which relieves the work-load of the approach controller by handling all the departures, and getting them away from arrivals as quickly as possible, leaving the approach controller free to handle arrivals (the hard bit).
|-
|xxxx_CTR
|(ARTCC) Center Controller
|Centers own all airspace not controlled by APP or TWR. They control the plane while en route, and get it from X to Y safely, until it can be descended and given to the approach controller.
|-
! bgcolor="#EFEFEF" align="left" |xxxx_FSS
! bgcolor="#EFEFEF" align="left" |Flight Service Station
! bgcolor="#EFEFEF" align="left" |Flight Service Stations cover large areas (e.g.: France) and provide support to pilots and controllers. They can advise pilots of weather and frequencies for other controllers. They do not provide Air Traffic Control.
|-
|xxxx_DEL
|Clearance Delivery
|Clearance Delivery is rarely used in FlightSims. In the real world, a controller would give a clearance (which explains where the plane is allowed to fly) to all planes, but the ease of giving a clearance in the virtual world, means the Tower can normally give the clearance.
|}

The 'xxxx' in the table replace a code used to identify the area that controller is using. These are known as [[ICAO]] codes, and can be found on the [http://www.airport-technology.com/icao-codes/ ICAO web-site]. For example, Heathrow is 'EGLL' so a Heathrow Tower Controller would log-in as EGLL_TWR.

Centers and flight service stations also have ICAO identifiers, but they are not for one airport, but for a larger area. For example, LFFF_CTR is France Center, and LFFF_FSS is the France Flight Service Station.

You may also see the callsigns xxxx_SUP and xxxx_OBS. These are used only in the virtual world and represent, respectively, a supervisor and an observer (someone who isn't controlling).

So now you can choose your position, but beware: if you are the approach controller at an airport which doesn't have a ground / tower controller, planes will expect you to offer them all those facilities, but if you are a London Center controller, you are not expected to offer center facilities to airplanes in an adjacent sector, but could be expected to offer very basic facilities of GND / TWR / APP to airports in your sector...

==Lesson 2==
Now, we'll have a look at each of the positions in details:

===_GND (Ground)===
Ground is possibly the easiest position available to controllers. The basic responsibility is to get planes to and from the runway and terminal buildings as quickly as possible (to save fuel and time) and to avoid planes colliding with each other. For this, you might need a GROUND SECTOR FILE. This is optional as a very detailed map of a particular airport (can be downloaded from the Sector System on IVAO) which hold all the taxiways as geographic data (press F5 to view).

Depending on the airport, the taxiways may have letters, or descriptions (e.g.: Inner Taxiway) or each section of the airport may have a number (called blocks). At Heathrow, the last two are used, so a statement like 'taxi to block 76 via the outer taxi-way' would be valid.

===_TWR (Tower)===
Tower has responsibility for all planes coming into or out of the airport, and the planes wishing to enter or cross the active runways. For Tower you can use any sector file with the airport shown, and center on your airport and zoom in to give your short (10NM) range. The first responsibility is to choose which runways to use (there's always at least 2 - one runway being used either direction) according to the weather (more later). You will also be expected to give IFR clearances, but this is very simple.

The biggest responsibility the tower has is to ensure that planes can take-off and land as quickly as possible, without any two colliding. Your approach controller should make sure that all planes arriving are well spaced and already heading directly for the runway. When a plane you've given permission to take-off to has left the ground, they are given straight to APP (Approach). Normally, there will not be a ground controller, so you may have to also give basic ground instructions (just ask a plane to get to the runway - not giving them directions - but warn them of any other traffic).

===_APP (Approach)===
Approach is the most complicated position. Approach controllers deal with all traffic arriving and leaving (unless there is a departures controller - unusual). The main aim, as always, is to keep the aircraft arriving and leaving separated. For departing traffic, the aim is to get them going in the right direction and give them to center as soon as possible; for arriving traffic, the aim is to get them onto the approach (the correct height and heading) so that they can follow an electronic system (the ILS) which gives them exact guidance onto the runway, and then you can hand them off to the tower, who will clear them to land and try and get planes taking off in between the landings.

The difficulty is, of course, dealing with the high volumes of traffic around an airport. In Lesson 3, SIDs and STARs are introduced which are standard ways of leaving from or arriving at an airport which ensure that planes maintain separation.

===_DEP (Departures)===
An unusual position in the virtual world, the departure controller controls all planes leaving an airport; normally _APP will handle these but sometimes traffic means that there is just too much for a single controller to do. It is the aim of the departures controller to get the departing aircraft away from the airport as soon as possible without interfering with approach's planes. Later, you will see that departures are kept below a certain altitude until they're a distance away so that any arrivals can fly over them without any mid-air collisions.

In this position you absolutely must co-ordinate very closely with the approach controller.

===_CTR (ARTCC - Center)===
Center handles all airplanes in a specific area which are en route and not getting ready to land or having just departed. They navigate the plane from place to place as quickly as possible whilst ensuring that planes stay separated from each other. A plane may deal with many centers as it passes over many countries in a flight.

Notice how I've mentioned separation in every description? SEPARATION is the first key to controlling. It does not matter how far out its way a plane has to go if you keep everybody on board alive. A pilot may well want to have landed five minutes earlier, but it's your job as the controller to keep them separated. Of course, having said that, the second key to controlling is expedite flow - that is keep traffic moving quickly and get it where it wants to go by the most direct route.

==Lesson 3==
Let's look at a plane taxiing to the runway and taking off now. So, to do this, we'll consider two controllers:
''ground control (_GND) and the tower (_TWR).''

First, we have to know which runway is being used so that ground can get the plane to the right place. The rule is 'planes always like to be heading into the wind for takeoff or landing'. The winds are given in the METAR like 'xxxyy'. The direction of the wind is given first in 3 digits, and the speed after that in 2 digits; so 11007 indicates winds of 7kts with a direction of 110 (magnetic heading). Winds under 5 kts can be considered 'calm' and can be ignored. Thus, the basic idea is to match the heading of the wind, and the runway heading (add a '0' to the runway number - 17L is 170) as closely as possible. Runways are numbered by knocking the '0' off the heading, and appending 'L' for left or 'R' for right if there are parallel runways.

At Heathrow, there are runways 9L and 9R, and the same runways (used in opposite directions) 27R and 27L. If the wind is 110º @ 15 kts then runways 9L and 9R are most suitable, as 90 and 110 are only 20 degrees away, but 270 and 110 are 160º away! At Heathrow, where there are parallel runways, one runway can be used for landing and the other for taking off - so a plane can be leaving on 9L while another is almost landing on 9R. Where there is only one runway, the same runway can be used to landing and taking off. It is important to notice that if an aircraft is taking off on runway 7, and another lands shortly after on runway 7, they are travelling in the same direction, so they are not approaching each other, and a collision is impossible.

Knowing about your ATIS which can be read by all planes to avoid you repeating information, you would want to put the active runways in your ATIS so that other controllers know which runways you have chosen, and so planes have an idea of what they will be expected to do. Always keep your ATIS short (as it is hard for the pilots to read a long ATIS), and delete any blank lines at the end. The other component of your ATIS should be the current weather, so a good ATIS for a tower or ground controller would be:

''London Heathrow Ground/Tower Information <alpha/bravo/charlie/delta/echo...>. Active runways are 9R for departures, and 9L for arrivals. Weather is'' '''(copy from METAR)''' ''110@15 FEW030 OVC090 Q1015 NOSIG. On initial contact report you have <alpha/bravo/charlie/delta/echo...>'' ; the only detail to note here is the use of alpha/bravo, etc. Each time you update your ATIS change the identifier up by one, so start with alpha, then use bravo, then charlie. This is used so that when a plane calls you and says 'information alpha' you know if he has current information or an old version.

Now that the active runway has been established and the ATIS set-up, you can go about controlling. First, though, you need to know some basic guidelines about contact. Usually, expect a plane to call you first. They should give their current location, callsign (used to identify each plane) and which ATIS they have, so:

'''B-ELIO: Ground, this is B-ELIO at the terminal, Information Alpha. Request clearance to Paris Orly.'''

B-ELIO, a plane, has called you telling you where he is, what information he has, and what he wants. To reply, you need to tell him whether the information is current ('Alpha is current') or new information ('New active runway is 23') and reply to his request.

First, we earlier mentioned IFR clearance. This allows the controller to know where the plane is going, and to plan ahead for the aircraft. If you remember looking at a Flight Strip in lesson 1, you will recall it allows a controller to see the destination of the aircraft, the route the aircraft will follow and the requested altitude. The aim of the clearance is just to confirm these details with the pilot, especially in the real-world where they may be altered due to traffic levels, to make sure there aren't any mistakes and everyone knows what's going to happen. The clearance is as follows:

'''<Callsign> is cleared to <destination> as filed''' (give any changes to the flight plan here). '''After takeoff c/m''' (climb and maintain) '''<altitude> on runway heading / and turn <left/right> to <heading>, expect <requested flight level> after 10 minutes. Squawk <transponder code>.'''

Here's an example clearance:

'''You: B-ELIO is cleared to Paris Orly as filed. After takeoff c/m 6,000 and turn left to heading 180 (south) expect FL310 after 10 minutes. Squawk 5201.'''

The clearance can be given whilst on the ground, and is given by Clearance Delivery (_DEL) if one is online, else the GROUND (_GND), or TOWER (_TWR) controller. The pilot must read-back the whole clearance, to which you confirm by saying 'readback correct'. The Squawk code is a number used to identify the plane. It can be seen on the flight plan (will default to 1200) and means - in the real world - a controller can tell the dots apart as each one has a number. Just assign an available number in the 5000 or 6000 range (eg: 6001, 6002, 6003, etc.).

'''B-ELIO: B-ELIO cleared to Orly as filed. c/m 6000 left 180 - expect FL310 after 10, and squawk 5201.''' 
'''You: B-ELIO, readback correct, call when ready to push-back and start-up.''' 
'''B-ELIO: B-ELIO requests start-up and push-back.'''

Here a push-back and start-up means he wants a vehicle to pull the plane away from the buildings so he can start his engines... this is a real-world call, and is not used in the virtual world, so just approve it. He might skip this entirely and just ask if he can taxi, otherwise say:

'''You: Cleared to push-back and start engines. Call when ready to taxi'''

B-ELIO will then call you when he's ready to taxi. Note you don't have to type B-ELIO, just click on his icon on the screen and ProController automatically inserts it for you. You can often just respond with 'roger' or 'rgr' which means you've heard what the other person has said, or 'wilco' which means you have heard and will obey. When he calls to taxi:

'''B-ELIO: rgr (to the push-back and start-up clearance). Ready to taxi to the active runway.''' 
'''You: B-ELIO, Taxi to runway 9 (or whatever Tower has chosen) and hold short, altimeter 1009.''' 
'''B-ELIO: to runway 9 and h/s, alt 1009, B-ELIO (h/s is short for hold short)'''

Hold short asks the plane to get close to the point given (here, the runway) without actually getting on to the point. Each runway has a line painted on the ground (the holding line) at which a plane waiting to take-off will wait until he is cleared onto the runway (tower's duty). If you put the plane on the runway, tower might be landing a plane and this plane might well land on top of it! The altimeter is given now so that you are sure that the plane has the correct altimeter setting, and is just good practice. Even with it in your ATIS, and their take-off checks, it never hurts to be safe. Your aim as ground is just to get a queue ready for takeoff so that tower has aircraft ready to takeoff when there's a gap in arrivals.

If the pilot needs to cross a runway, he'll stop before the runway and ask for clearance. You just direct him to ask the tower for this information. Imagine for a second that there's another plane taxiing to the runway as well... tell the plane to give way:

'''You: B-ELIO, Taxi to runway 9 and hold short. Give way to the American Airlines 747 taxiing from left to right.'''

Now the pilot will have to give way to the 747 moving in front of him from his left to his right. If B-ELIO was also an American Airlines, you can use the word 'Company' to mean 'of the same company' so 'Give way to company 747...' would be legal. As a ground controller, with a detailed map, you might like to give full details of the way you want him to go, but normally the controller can just give a simple statement like the ones above:

'''You: B-ELIO, taxi via Inner Taxiway to block 53, then left onto taxi-way B to runway 9, and hold short.'''

Now the plane is ready to get onto the runway and takeoff, you hand him off to TWR, using the method you learnt in Lesson 1 by right-clicking on the plane, selecting 'aircraft >' and then 'request handoff' and select the appropriate controller. This will ask the controller for a hand-off and, when they accept, the circles around the plane will change colour, you can now go through the same menu and choose hand-off which will give B-ELIO the following message. In the real world, you'd actually say it, and in IVAO, you can just type it without using the automated system:

'''You: B-ELIO, contact the tower frequency 119.7 (you'd have to look up the frequency in who is on-line)'''

So now, it's Tower's turn to get this plane off into the sky...

If you were awaiting a plane to land, you could just leave the plane queuing, but if you are ready to have him on the runway tell him to get into position on the runway. Remember, it is your job to get aircraft onto and off the runways as quickly as possible, so that planes can land and take-off quickly:

'''You: B-ELIO, runway 9, line up and wait.''' 
'''B-ELIO: Runway 9, line up and wait, B-ELIO.'''

One thing to note, the phrase 'position and hold' is no longer used, since the FAA adopted the ICAO standard "line up and wait" (since September 30, 2010).

You may also use a conditional clearance, to make your job easier:

'''You: B-ELIO, runway 9, line up and wait [after the arriving B747 / following the departing B757]'''

The plane may give a call back when he's ready like 'ready for departure' or 'on the numbers'. If not, just wait until his icon stops moving and give him his takeoff clearance:

'''You: B-ELIO, winds calm/110@15, runway 9, cleared for takeoff''' 
'''B-ELIO: Cleared for takeoff.'''

The plane will commence his take-off roll, and - as soon as he is airborne - you want to get rid of him and get onto your next plane. You initiate the hand-off to approach, and handoff as soon as (s)he accepts. So now, onto approaches dealings...

==Lesson 4==
''(In this section the approach controller is presumed to be handling departures, as there are very, very rarely departure controllers. If there were a departure controller, (s)he would deal with a departing plane, and the approach controller would deal with any planes arriving)''

So approach now has a plane that wants to get on with its flight. The first thing to notice was the clearance:
''climb and maintain 6,000...''

It wasn't explained last page, but the reason for this low height is to ensure that planes arriving at the airport - also at low heights - that are arriving from the takeoff end of the airfield are kept above the departing planes. If arriving planes are only cleared down to 8,000 ft. then - even if they have to fly over the airport and turn around - they cannot conflict with departing planes. For this reason, departing planes are usually cleared to 6,000 and arriving planes to 8,000 until they are on the 'safe' (non-departure) side of the runway.

Let's look at how the hand-off occurs this time:
'''EGLL_TWR: B-ELIO, contact EGLL_APP on 119.72, good-day.''' 
'''B-ELIO (to you): Heathrow Approach, good-day, this is B-ELIO out of 1,700 for 6,000 on runway heading'''

This time, because the plane is in the air, you want to acknowledge you can see him on the radar:
'''You: B-ELIO, Radar Contact, continue to 6,000... (and right to 120)'''

The aim now is to get the plane heading in the right direction (that is, towards the first VOR or NDB - remember how they're shown on the display - listed in the Flight Strip, or just in the general direction of the country he's heading to. When the planes far enough away from the airport, or there's no other traffic, climb him up to 12,000 - 18,000ft and hand him off to center. Now, a few words about giving the plane vectors (headings), remember:

* Don't expect the plane to respond instantly... think ahead. By the time he's got your message and started to turn he might be 1 NM further on that you expected.
* If he's heading directly to a 'fix' (any VOR, NDB or Intersection) give them a 'direct <place>' order like 'B-ELIO, turn left direct BIG' - don't bother trying to figure out headings when you've been given an easy way.
* Consider your heading -- are you sure you mean 90 and not 270? If the aircraft is heading to the left of the screen, he's flying a heading of 270 and not 90!! This may seem obvious, but is one of the biggest problems for new controllers.

Now the plane's in the sky, a big, bold few words about separation:
'''Keep your planes at least 3NM from each other, or at least 1,000 ft vertically between them. If you think the planes will eventually come too close, don't wait -- turn or descend one immediately! In order to make collisions between planes traveling in opposite directions less likely, use this rule:'''

{| class="prettytable"
! align="center" bgcolor="#EFEFEF" |
! align="center" bgcolor="#EFEFEF" |
|-
|Plane flying headings 0-179
|Fly at ODD FLIGHT LEVELS
|-
|Plane flying headings 180 - 359
|Fly at EVEN FLIGHT LEVELS
|}

What are Flight Levels? Flight Levels are used to shorten heights -- you should recognize them from the plane's blip -- you simply remove the two last digits from the height, for example 32,000ft --> FL320. Also, when you talk about Flight Levels, the pilot uses a standard altimeter setting (instead of the local altimeter setting found after the Q in the METAR weather report in the bottom right of your screen); while at low altitudes the plane will use the local barometric pressure. This means that all planes cruising will think 32,000 ft is at the same place, and not vary slightly depending on the local pressure.

Your aim is to get the planes in the right direction at a height ready for hand-off to an ARTCC (_CTR) and away from the airport. Once you've done it pass your plane onto the centre controller. It is a good idea to use the .chat <callsign of controller> function to ensure that you and your center agree on what places and heights you'll hand off at.

Now the planes with Centre. The same hand-off procedure as above applies... wait for the first contact. When you've got it, identify the plane, and report 'radar contact'. If a plane is in your airspace and won't contact you try asking on your frequency, then try a quick switch to 121.50 to send a 'Contact EGTT_CTR on 132.600' to get the plane's attention. Using 121.50 (the Guard Frequency) is used when you can't contact a plane -- all planes within a few hundred miles will hear your broadcast, irrespective of who it was intended for! Remember to switch back to your frequency -- you don't want everyone to hear your broadcasts for the rest of eternity (or perhaps you do; I certainly don't).

Centers job is pretty easy until its busy. Read the planes intended route and just get the plane to fly it. If there are other planes, make sure they don't collide. Since opposite traveling planes will have a 1,000 ft separation (using the table above) you shouldn't need to worry that much. Other than that, listen to the pilot's requests and help him where you can. When you get to your ARTCC boundary hand-off to the next centre, or - if there isn't one - give the order:

'''You: B-ELIO, no control available in France, resume own navigation to Belgium, radar service terminated'''

This statement removes all your requirements to control the plane, as it now knows that your not watching on radar, and you're not going to help him navigate. When you are navigating as centre - if the flight plan doesn't include a route - find the start and end points, and plan a quick route (either direct - give one heading - or by 'hopping' from VOR to VOR).

These terms are used often while controlling to confirm or deny requests and answer any questions:

{| class="prettytable"
! align="center" bgcolor="#EFEFEF" |
! align="center" bgcolor="#EFEFEF" |
|-
|Affirmative (sometimes affirm or aff)
|Yes or correct
|-
|Negative (sometimes neg)
|No or incorrect
|-
|Confirm...
|Is it correct that...
|-
|Unable...
|Sorry, I cannot accept your request for...
|-
|Roger (almost always rgr)
|I've heard and understood your last transmission
|-
|Wilco
|I will comply with your orders (implies Roger)
|-
|Standby (sometimes stby)
|Please wait, I will call you back when I am free.
|}

'''Some examples of these:'''
* '''You: Confirm current altitude is FL310. '''
**'''B-ELIO: Negative, FL290'''
* '''B-ELIO: Request descent to FL290 '''
**'''You: Unable FL290 (there is already traffic at FL290?)'''

When the plane is nearing its final destination, make sure it has descended to between 18,000 and 22,000 ft. This means that the approach controller can take the plane and descend it quickly -- it's no good trying to descend a plane 35,000 ft in 20 NM and still get it to land. Notice that the plane should remain above 18,000 ft (in your airspace) until you've handed off. Approach might decide not to take the plane and have you make it fly circles in the sky for 20 minutes until he has some room; otherwise arrivals and departures might crash while they're being handed over! So:

'''You: B-ELIO, d/m (descend and maintain) 18,000 on QNH 1221, right to 270 and expect hand-off to approach in five minutes.''' 
'''B-ELIO: down to 18,000 on 1221, will expect approach in five, B-ELIO.'''

What is the QNH? This is an altimeter setting. As the plane will shortly be moving back to local pressure, and not the flight level standard pressure, the pilot must know the local pressure. This ensures that his diagrams which give him the height of the airfield above sea level are correct -- if everyone used a standard altimeter setting at low altitudes the airport's height would seem to fluctuate over a period of hours by a few hundred feet! And finally:

'''You: B-ELIO, contact EGLL_APP on 192.72'''

I'm not sure how we ended up at Heathrow, but that's another story!

==Lesson 5==
Our plane, B-ELIO, is now about 40NM east-south-east of Heathrow ready to start the approach to runway 9L - as tower has chosen runway 9R for departures, with the winds of 87@22 - the plane is at 18,000 ft and is heading at 270 (towards the left of our screen...).

Did you remember that the landing direction would be towards the right of the screen? I hope so... Anyway, planes need to be at 2,500 ft about 8NM away from the airport heading in the correct direction to intercept the magical [[ILS]] device that will guide them perfectly onto the runway. We know we need to keep the plane at 8,000 ft until its past OCK, and then get it down to 2,500 and onto the grey dotted line leading to the left runway (9L) for the ILS and tower to take the passengers safely to the ground. Formulate a plan: accept the hand-off, descend the plane to 8,000 and send it directly towards OCK VOR, at OCK descend it to 2,500 and fly it past OCK on 270, then turn it to 360 (north, easier to read than '0') up the grey dotted line pointing north, then turn it to 45 so that is cuts the grey-dotted line at 90 to runway 9L... when the plane is on a course taking it through extended center-line (an imaginary line representing a line extending from the runway) it is said to be intercepting the localizer. The plane can then be told to get itself onto this extended center-line as the ILS will warn the plane when it needs to turn to establish itself on the line.

Since the airplane is on the wrong side of the airport, we fly three sides of a rectangle, the first is known as the down-wind (since you land heading up-wind), then the next 'leg' is known as the base, and the red-line shows the final. If the plane was coming from the west, he could just fly a 'straight-in' approach, also known as an extended final - as the plane only flies a very long final.

The orange line shows the 'intercepting the localizer' as the plane will continue to fly this heading until the ILS tells it to turn right onto the center-line of the runway. As soon as the plane reports it's established on the localizer (it has direction signals), it can be cleared for the approach and told to descend with the glideslope which gives the plane height signals. The glideslope and localizer give precision approach information and are known - together - as the ILS (Instrument Landing System). Then get the plane to the tower, because - remember - you may well be dealing with planes taking off which you need to get out of your air-space, and other planes trying to get established on the ILS, as the tower wants a steady stream of well-separated planes on the ILS. You hopefully now know what you're supposed to be doing, but how do we do it. We'll look at each stage in turn.

'''B-ELIO: B-ELIO with you at 18,000 for Heathrow. Information Alpha. (Your ATIS - might contain weather, voice IP?)''' 
'''You: B-ELIO, Radar Contact, alpha is current. d/m 8,000 and direct OCK please.''' 
'''B-ELIO: rgr, down to 8,000 to OCK.'''

Great... B-ELIO will now get to OCK and be at 8,000. Just before he gets to OCK, you need to issue the next instructions so that he can be ready for them:

'''You: B-ELIO, d/m 2,500 continue present heading and expect ILS approach to runway 9L at Heathrow.''' 
'''B-ELIO: rgr, 2,500 on my heading for 9L, B-ELIO.'''

OK so far? Now let's head him towards the airport. This is the base leg:

'''You: B-ELIO, turn right heading 360 (for base) the for base is for information and is usually left out.''' 
'''B-ELIO: t/r (turn right) 360, B-ELIO'''

This is where judgment and cunning use of the feature for monitoring heading and distance come into play. It is also your duty to give the plane the frequency for the ILS (in the form xxx.xx) which can be found at www.ivao.aero/db/ss (or from database, sector system) using the search facility. The plane just hit the extended center-line at least 8NM away from the airport, so make sure you issue the turn to 45 at the correct time, otherwise B-ELIO will miss the ILS. Right place, so...

'''You: Turn right heading 45 to intercept the localizer on 119.21 to 9L and report established.''' 
'''B-ELIO: right to 45 for LLZ to 9L, will report established'''

B-ELIO will now get himself onto the localizer and call:

'''B-ELIO: established'''

This is your cue to clear him for the approach and allow him to descend (otherwise he'll fly perfectly over the runway at 2,500ft). This is done with the following command:

'''You: B-ELIO, rgr (I heard the 'established') cleared the ILS approach to 9L, descend with the g/s. 
B-ELIO: Cleared ILS approach.''' 
'''You: B-ELIO, contact the tower on 118.52 (if there is a tower, else you'll have to do the job... and look up the tower frequency in who's on-line)''' 
'''B-ELIO: Over to the tower, thanks for your help.'''

That's your job done! As the approach controller you have the most work, so don't be afraid to give planes holds. A hold is a request for a plane to circle around a given fix (e.g.: a VOR) at a given height until you can do something with them. In fact, if you have lots of planes all circling a VOR, it's known as a 'stack' because the plane's are stacked there. So, we could get three planes holding at the OCK VOR (while we waited for traffic to decrease) at 6,000 ft, 8,000 ft and 10,000 ft and add new planes to the top and take planes ready for the approach from the bottom. To give a hold, the basic command is:

''Hold at <vor name> VOR at <current altitude/10,000 etc. / FL120 etc.>, expect further clearance in <time> minutes.''

Which requests the pilot flies around the <vor name> VOR at the assigned altitude until you give him a new clearance. The expect further clearance (e.g.: expect further clearance in 10 minutes) just gives the pilot some idea of the delay and does not give the pilot the right to start flying away after that time is over! The full clearance for holding is as follows, but usually you can just use the one above unless you specifically need to avoid a plane coming to a certain side of the VOR:

'''Hold <north/east/south/west> of the <vor name> VOR on the <approach heading> radial, expect further clearance in <time> minutes.'''

The approach heading is the heading at which you want the plane to approach the VOR. So, hold north of the OCK VOR on the 270 radial would ask the pilot to fly to OCK on a hdg of 270 and then to hold so he's always north of the fix. A hold is a racing track shaped rectangle.

The key to remember as the approach controller is to, wherever the planes coming from, remember its height is just as important as its direction when it comes to landing - 2,500 ft (above ground level) for the ILS.

Disaster! You've got a propeller aircraft doing an approach and you've started a 747 on the same approach behind it. There's nothing to hold it at, and there getting very close -- what do you do? You could take the plane away and start the approach again, but using an orbit -- a circle to the left or right and then on the original heading -- will increase your time, just give:

'''You: B-ELIO, one orbit to the left please for spacing.''' 
'''B-ELIO: wilco'''

Also, sometimes as approach you will want to slow a plane down to ensure that it isn't conflicting with a plane already on approach in front... if they are too close, the second plane will end up missing his approach because the plane in front will still be on the runway.

'''You: B-ELIO, slow to 210kts''' 
'''You: B-ELIO, slow to minimum feasible speed please''' 
'''You: B-ELIO, maintain minimum 190kts ''etc.'''''

Anyway, back to our imaginary flight in which B-ELIO is flying the approach and is back with the tower...

==Lesson 6==
Tower now has B-ELIO who is now cleared for the ILS approach, so can descend to the decision height. The decision minimum height is the height above the airport to which the plane can descend before being cleared to land. The plane cannot pass the decision height until he has visual contact (that is, he can see) the runway he wants to land on. If he cannot see the runway he will execute a missed approach and go around for another approach.

The pilot will report to the tower:

'''B-ELIO: B-ELIO with you to land 9L.''' 
'''You: B-ELIO, Rgr. (you do not need to give radar contact, as the pilot no longer needs a radar service. He is using ILS)'''

You can then give the landing clearance, or - more likely - you can delay the clearance until he is 8NM from the airport and so are more certain that he will be able to land. The 8NM point of the approach is marked by a special device that causes a tone and light in the plane's cockpit. This device is known as the outer marker (O/M or OM). You can ask the pilot to tell you at this point for his clearance:

'''You: B-ELIO, report the O/M for landing clearance''' 
'''B-ELIO: rgr 
'''B-ELIO: at O/M'''

'''You: B-ELIO, winds 109@17, runway 9L, cleared to land.''' 
'''B-ELIO: 9L, cleared to land, B-ELIO.'''

Your aim as the tower is to clear the plane to land to avoid it having to miss its approach, and get other planes taking off between the landing planes, whilst maintaining separation between the planes. You must remember to account for the fact that a plane trying to land may miss its approach, and have to fly past the airport -- so make sure you turn slower planes away from the airport quickly in case a jet needs to continue past the runway.

After B-ELIO has landed, while he's still on the runway, you still control him. You want him off your runway as soon as possible, so you can land the next plane (otherwise, if he's still anywhere on the runway, you'd have to give a landing plane a missed approach), so:

'''You: B-ELIO take first taxi-way to <left/right> then contact ground on 121.65 (look up frequency in who's on-line)''' 
'''B-ELIO: Thanks for your help, switching to ground.'''

And your job is done... let's look at a worse scenario. You landed a plane before B-ELIO and for some reason it hasn't been able to get off the runway yet. You must not let B-ELIO land whilst any other plane is on the runway, so you order B-ELIO to miss his approach:

'''You: B-ELIO initiate missed approach immediately, c/m 6000 on runway heading, and contact approach on 192.72 (again, use who's on-line) 
B-ELIO: Missed approach, and will contact approach.'''

Approach will then climb the plane back to 6,000 ft (as it is almost a departure now) and complete the down-wind and base legs again (possibly on the other side of the airfield, depending on traffic). The plane can then be vectored back onto approach by the approach controller, and then given back to tower to try again. Of course a plane can initiate their own missed approach.

'''B-ELIO:''' No visual on runway, going around (same as missed approach), B-ELIO. 
You: Rgr, c/m 6000 left to 60 (perhaps there's traffic straight ahead?) and contact approach on 192.72.'''

Once, B-ELIO is back with the ground controller, having taxied just off the runway, he will be given instructions to taxi to the terminal building. If there is no ground, the tower controller can just give a 'taxi to parking' order without specialized instructions.

That concludes the average flight in ProController, but the next (and last) page of this lesson contains some information that you may want to know, for example: the words used to represent single letter (e.g.: alpha for A in ATIS, and lima for L as in 'taxi-way lima' as opposed to 'taxi-way L').

[[Category:Air Traffic Control]]

Talk:Splash screen requests

2010-10-30T23:50:56Z

Airbird1:

This page is a stub. Will be deleted if not used.

--Callsigns: KOAK_CTR, Airbird1 04:54, 27 October 2010 (UTC)
:: No, it will not be deleted :-) See the latest forum "wishlist" thread, I am trying to clean up the wiki and archive important forum requests using the wiki, see here: http://wiki.flightgear.org/index.php/Volunteer#Artwork_Creators.2FContributors If you know a better way for doing this, please go ahead! So, I do welcome your help - but please don't step on my feet, thanks! --[[User:Hooray|Hooray]] 06:25, 27 October 2010 (UTC)

::: Whoops. But you might need to advertise the page a little bit, seeing as not a lot of people are using it.

--Callsigns: KOAK_CTR, Airbird1 23:50, 30 October 2010 (UTC)

Talk:Splash screen requests

2010-10-27T04:54:11Z

Airbird1: PLEASE SEE

This page is a stub. Will be deleted if not used.

--Callsigns: KOAK_CTR, Airbird1 04:54, 27 October 2010 (UTC)

Boeing KC-135E

2010-10-27T04:51:53Z

Airbird1:

{{infobox Aircraft
|image = KC-135E.jpg
|name = Boeing KC-135E
|type = Military aircraft
|fdm = JSBSim
|status = Alpha
|authors = Innis Cunningham, Vivian Meazza, David Culp and Julien Pierru
|fgname = KC135
|download = http://www.flightgear.org/Downloads/aircraft-2.0.0/
}}
The '''Boeing KC-135 Stratotanker''' is a United States aerial refueling tanker [[aircraft]]. It has been in service with the United States Air Force since 1957. The KC-135E is the only user-controlled tanker aircraft available in [[FlightGear]] at the moment.

The maximum fuel load is 200,000 lb (90,719 kg) or 31,275 US gal (118 kL).

==Aircraft help==
The boom will extend automatically when the aircraft's gear is retracted.

* [[Howto: Air-Air Refueling]]

==Download==
You can download the KC-135 at the default FlightGear [http://www.flightgear.org/Downloads/aircraft-2.0.0/ download website]. Or just look at the sidebar to the right. :) -->

==Development==
INFO AS OF MID-OCTOBER 2010
This list has not been finalized.
I am not sure, please correct me if I am wrong, but for the Standard Version of the KC-135E, there needs to be:

* Reverse Thrust
* Pushback (If not yet in, will be developed by Airbird1)
* Actual KC-135 cockpit (the current one is a 737-800)
* Perhaps a development on the Aircraft Help?
* Liveries

{{Boeing}}

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

Boeing KC-135E

2010-10-27T04:50:54Z

Airbird1: Added list of unsureties

{{infobox Aircraft
|image = KC-135E.jpg
|name = Boeing KC-135E
|type = Military aircraft
|fdm = JSBSim
|status = Alpha
|authors = Innis Cunningham, Vivian Meazza, David Culp and Julien Pierru
|fgname = KC135
|download = http://www.flightgear.org/Downloads/aircraft-2.0.0/
}}
The '''Boeing KC-135 Stratotanker''' is a United States aerial refueling tanker [[aircraft]]. It has been in service with the United States Air Force since 1957. The KC-135E is the only user-controlled tanker aircraft available in [[FlightGear]] at the moment.

The maximum fuel load is 200,000 lb (90,719 kg) or 31,275 US gal (118 kL).

==Aircraft help==
The boom will extend automatically when the aircraft's gear is retracted.

* [[Howto: Air-Air Refueling]]

==Download==
You can download the KC-135 at the default FlightGear [http://www.flightgear.org/Downloads/aircraft-2.0.0/ download website]. Or just look at the sidebar to the right. :) -->

==Development==
INFO AS OF MID-OCTOBER 2010
This list has not been finalized.
I am not sure, please correct me if I am wrong, but for the Standard Version of the KC-135E, there needs to be:

* Reverse Thrust
* Pushback (If not yet in, will be developed by Airbird1)
* Actual KC-135 cockpit (the current one is a 737-800)
* Perhaps a development on the Aircraft Help?

{{Boeing}}

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

Boeing KC-135E

2010-10-27T04:44:23Z

Airbird1: Just a minor addition

{{infobox Aircraft
|image = KC-135E.jpg
|name = Boeing KC-135E
|type = Military aircraft
|fdm = JSBSim
|status = Alpha
|authors = Innis Cunningham, Vivian Meazza, David Culp and Julien Pierru
|fgname = KC135
|download = http://www.flightgear.org/Downloads/aircraft-2.0.0/
}}
The '''Boeing KC-135 Stratotanker''' is a United States aerial refueling tanker [[aircraft]]. It has been in service with the United States Air Force since 1957. The KC-135E is the only user-controlled tanker aircraft available in [[FlightGear]] at the moment.

The maximum fuel load is 200,000 lb (90,719 kg) or 31,275 US gal (118 kL).

==Aircraft help==
The boom will extend automatically when the aircraft's gear is retracted.

* [[Howto: Air-Air Refueling]]

==Download==
You can download the KC-135 at the default FlightGear [http://www.flightgear.org/Downloads/aircraft-2.0.0/ download website]. Or just look at the sidebar to the right. :) -->

{{Boeing}}

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

Howto:Improve framerates

2010-10-26T00:30:44Z

Airbird1: Fixed headings, added 3 sections.

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

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

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

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

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

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

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

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

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

==Outside vs. Inside Views==
One of the things that can also affect the frame rate is the view. The inside cockpit view is better than the outside views, like Tower View (especially KSFO) and Chase view without Yaw. Once inside, the GPU and/or graphics card does not have to draw scenery. But if the cockpit is 3D and really detailed, performance is about the same.

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

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

[[Category:Howto|Improve Framerates]]