Fr/FlightGear

2012-08-30T08:11:43Z

Sahliyoussef: Created page with "{{Infobox Software | title = FlightGear | logo = fglogosm.jpg | image = FlightGear - 1903 Wright Flyer.jpg | alt ..."

Howto:Understand console output

2012-08-30T03:41:34Z

Sahliyoussef:

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 ==
=== Aircraft uses deprecated node egt_degf. Please upgrade to egt-degf ===
The aircraft should be updated to make use of the renamed egt-degf property but it will still work as expected. You could contact the aircraft's author but he/she is probably already aware of this.

=== Airports/.... ... Done ===
This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG SCENERY]]/Airports</tt> directory.

=== Bad operation output detected in configuration file ===
[[JSBSim]] reports that a <output> tag is incorrectly placed in the aircraft's FDM. When used in a <fcs_function>, it should be outside the innter <function> tags, so like:
<syntaxhighlight>
<fcs_function name="Flap Cmd Deg">
<function>
<product>
<property>fcs/flap-cmd-norm</property>
<value>30</value>
</product>
</function>
<output>fcs/flap-cmd-deg1</output>
</fcs_function>
</syntaxhighlight>

=== Base package check failed ... Found version ... at: ...<br />Please upgrade to version: ===
When using [[Git]], the data must match the binary or compilation. You cannot use data from a different date than the binary's release date.

=== Base package check failed ... Found version [none] at: ...<br />Please upgrade to version: ===
FlightGear was unable to find the [[$FG ROOT]] directory. Set it using the <tt>--fg-root=</tt> commandline option.

=== Cannot find specified aircraft ===
Shows up when you use an incorrect aircraft name in the --aircraft=... command. Check the correct name by running --show-aircraft, or by looking at the aircraft's -set.xml file (eg. <tt>--aircraft=737-300</tt> for <tt>737-300-set.xml</tt>).

=== 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()<br />SG_IO_OUT socket creation failed ===
Your computer is not connected with the internet, while a certain enabled feature (eg. multiplayer) does require an internet connection.

=== 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. Note that you might need to enable a scenario in combination with a --carrier= command.

'''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: illegal character after . or .. ===
Some .xml file contains a fault. Possible solutions:
* To refer to a top-level property in the tree, <tt>../</tt> should be used instead of <tt>.../</tt>

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

=== Failed to tie property fcs/ to object methods ===
This [[JSBSim]] error comes up when there are unnamed components (eg. switches) in the FDM of an aircraft. Components must have unique names, from which properties will be created. As long as you are not overwriting an existing property, the <tt>name="..."</tt> can be used to output the components result to a property.

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

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

=== 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 ...<br /> In component: ... unknown property ... referenced. Aborting ===
FlightGear found a reference in the [[FDM]] to a non-existing property.

=== FGPropertyManager::GetNode() No node found for ...<br /> 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<br />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'<br />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 ===
[[File: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: unexpected } in sign contents ===
One of the OBJECT_SIGN lines in the .stg file (of the tile that was loaded when this error showed up) contains a fault. Note that <tt>}</tt> must be preceded by a <tt>{</tt> character.

=== 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><br />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 [[Git]] version or solve the problem yourself and let someone commit the patch.

=== OpenAL error (AL_INVALID_VALUE): constructor (alBufferData)<br />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.<br /><br />'''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.
* Make sure you did set the right executable (<tt>fgfs.exe</tt>) on the first page of the [[FlightGear Launch Control]].

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

=== Unknown exception in main loop. Aborting...<br/>Possible cause: Not enough space ===
See [[Howto: Improve framerates#Optimus Technology]].

When your computer does not have the Optimus Technolog (NVidia) or Hybrid Graphics technology (ATI), you are likely to be unable to run FlightGear. Integrated graphics cards are very weak; too weak for FlightGear. You can try to switch of some of the eye-candy though, but even then the same error may appear...
It may be useful to check the latest drivers for your graphic card.
•If you have a Nvidia GPU, then visit http://wiki.flightgear.org/Howto:Improve_framerates#nVidia.
•For '''ATI line''' of video cards, look at this site: http://www.amd.com/us/products/technologies/amd-catalyst/pages/catalyst.aspx .You should find a file named "Catalyst control center", which allow you to modify the behaviour of your GPU with flightgear. I mean the Antialiasing control, the triple buffering, etc.
=== 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:<br />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.

=== YOU HAVE AN INCOMPATIBLE CFG FILE FOR THIS AIRCRAFT. RESULTS WILL BE UNPREDICTABLE !! ===
Make sure the [[JSBSim]] [[FDM]] of the aircraft has a <code><fdm_config version="2.0"</code> tag.

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

=== 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 ===
[[fr:Howto: Débarrassez-vous des erreurs les plus fréquentes]]

[[Category:Howto|Console output]]