Howto: Get rid of common errors
From wiki.flightgear.org
This document lists common FlightGear errors and how to get rid of them. If FlightGear quits but does not give you any error, try increasing the Log Level.
Errors with solutions
Base package check failed ... Found version [none] at: \FlightGear
Please upgrade to version:
FlightGear was unable to find the $FG_ROOT directory. Set it using the --fg-root= commandline option.
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.
Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified=
Try changing the 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 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: 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 open file ...
Check if the file exists on your system. If the missing file is a scenery object; be sure you have the latest Shared Models from the FlightGear Scenery Database.
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.
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 multiplayer has not been set.
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 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.
Near camera not rendering
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.
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 aircrafts 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 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...
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.
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 C:\Users\Owner\AppData\Local\VirtualStore and seeing if you have a folder called FlightGear in there. If you do, cut-and-paste (merge) that one with C:\Program Files\Flightgear 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
Unable to choose requested pixel format
Error should be solved as of version 1.9. If not, try changing your BPP and/or resolution.
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.
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 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 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: Picked up TriangleIntersect
Reduce your Log Level to alert. Or 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.
Errors without solutions
Please take a look at the upcoming errors and see if you know a solution to get rid of them. Your additions are grealy appreciated!
