From FlightGear wiki
This document lists
errors, how to get rid of them and other console output. If FlightGear quits but does not give you any error, try increasing the .
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.
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.
This is not an error. The message lets us know that
is updating the /Airports directory.
This error indicates that an argument the function is either the wrong type or does not exist.
It is accompanied by a line showing the location.
For instance, executing the below snippet in the
will throw the error blow the snippet.
var hash = {
element: &value&
append(hash, &string&, 12, 5.67); # you can only append() to a vector
bad/missing argument to append():
at &nasal-console/#1&, line 4
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:
	&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&
When using , the data must match the binary or compilation. You cannot use data from a different date than the binary's release date.
FlightGear was unable to find the
directory. Set it using the --fg-root= commandline option.
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. --aircraft=737-300 for 737-300-set.xml).
A condition (like &less-than& or &equals&) exists, without either:
a property to check
a value to check the property against
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.
Tells you that a new noise texture is created. It is not an error and can be ignored.
Try changing the
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.
When using
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.
Make sure that your data and source (or binary) match. They must be from the same date, to provide the best performance.
Your computer is not connected with the internet, while a certain enabled feature (eg. multiplayer) does require an internet connection.
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 .
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).
FlightGear is unable to find a
under the set name. Check your commandline (--carrier=...) or the
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
for details.
Check if the file exists on your system. If the missing file be sure you have the latest
from the .
Some .xml file contains a fault. Possible solutions:
To refer to a top-level property in the tree, ../ should be used instead of .../
In some .xml file, an opening tag (like &sim&) does not match its closing tag (like &/sim&). This error is hard to track down, best method is to comment (place code between &!-- and --&) 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.
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.
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 name="..." can be used to output the components result to a property.
A token (&!-- --&) has been started, but not closes. Add --& 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.
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.
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.
FlightGear
has not been set.
FlightGear found a reference in the
to a non-existing property.
FlightGear found a reference in the
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.
This one is caused by wrong line ending in a timezone file. Solution might be to download the Timezone/time.tab file manually from
(Right mouseclick & Save target as) and overwrite the file in /Timezone/time.tab with it.
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.
This reports that you do not have proper hardware accelerated 3D (direct rendering) configured.
A startup location in the
is not (properly) connected to a taxi route. Contact the airport author, or import the network to
and run the Verify network command to find the corrupted gate.
U they have to support atleast OpenGL 2.0 for FlightGear 2.0 and later.
This is not an error. It shows that an
is loaded.
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 -set.xml in the root directory of the loaded . 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.
This error is
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
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 's -set.xml file or by adding a
to the script.
if this error is shown for a /Nasal/ script.
If you are using non-English characters, your
path may need to be temporally changed:
Create a new empty folder such as C:\temp. Don't include non-English strings in the path.
At the last page of the Flightgear launcher (FGRun), click the [Advanced...] button, select Environment, click [New] button, enter FG_HOME=c:\temp in the field and click [OK].
If you screen looks
make sure you have at least
version 2.7.6.
(or binary) and your data directory.
(or binary) and your data directory.
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.
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 } must be preceded by a { character.
Check the OBJECT_SIGN lines in the .stg file of the tile that was loaded when this error showed up.
This error is probably displayed because of some misdirected audio settings in the
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
version or solve the problem yourself and let someone commit the patch.
Disabling sound is a temporarily solution for this problem.
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.
Tells you that an effect binded certain attributes to a .
(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
. Use some small value like 0.001 instead.
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.
In short, your GL libraries are broken. So far only Red Hat 7.x users have experienced this (see ). The only solutions are possibly complicated ones: you can either change distributions (most of us prefer Debian) or upgrade/downgrade your Mesa libs.
If you are running Windows V 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.
Make sure you did set the right executable (fgfs.exe) on the first page of the .
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 . Run as `d2u *.tab` from within the timezone directory to fix your timezone files
There is either an airport missing from apt.dat, or there is a wrong ICAO code in a . An airport missing from apt.dat could be due to a recent opening.
Error should be solved as of version 1.9. If not, try changing your
and/or resolution.
This error can be surpressed by disabling , via the AI/ATC .
The error appears when an airport in /Airports/apt.dat.gz cannot be found in /ATC/default.tower and /ATC/default.atis. Renaming the airports in the apt.dat.gz file ór in both default ATC files will fix the problem.
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!
FlightGear found a non-existing tag in the
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: --fdm=... should be left out.
: Advanced & Flight Model should be set to jsb (which will leave the whole command out of the commandline, so you can use this setting with any FDM).
FlightGear is unable to load the forced
(set through --fdm=... or via Advanced & Flight Model in ) 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 jsb; that is the "auto setting".
This error could have a variety of sources, among them missing files but also other things. Increasing the
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
to a lower value might work.
Changing the resolution to a smaller one might work as well.
When running 64 bits Windows, make sure to uncheck the "force 32-bits" option on installation.
Most notebooks that run Windows 7 have the so called Optimus Technology (NVidia) or Hybrid Graphics technology (ATI) onboard. This is meant to increase battery life, by automatically switching of the powerfull graphics card when it's not needed. However, FlightGear needs it all the time, even if Optimus says it doesn't! See
for instructions on how to disable this behaviour.
When the above mentioned points do not apply or did not work, you are likely to be unable to run FlightGear at the current graphics settings. See
for instructions on how to switch off demanding eye candy.
Apart from the above mentioned stuff, it may be useful to install the latest drivers for your graphics card:
If you have a Nvidia GPU, then visit .
For ATI line of video cards, look at this site:
.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.
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.
A library is missing from your computer. Therefore, certain fileformats cannot be read. Try to reinstall/update , as the libraries used by FlightGear should be part of the standard package.
Reduce your
to alert. Or . The errors might still be shown, but do not affect the sim anymore.
This is an
error, showing up when an effect needs tangent vectors, but polygons are not support. The error itself can be ignored, altough some
may look wrong. Shader developers should try to minimise the use of polygons and use triangles and quads instead.
Some control in the
is too weak, according to YASim, to control the aircraft. An effectiveness tag will be required in the FDM to solve this error.
There is a problem in the . A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.
Make sure the
of the aircraft has a &fdm_config version="2.0" tag.
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!
The sound effect's pitch (high or low) and gain (volume multiplication factor) values are not valid.
Has something to do with the
scripting language used by FlightGear.
A JSBSim error.
error, possibly you (or the developer) have/has not specified a texture for a surface while modeling the aircraft model in AC3D, Blender, Wings...
You (or the developer) have/has not specified a proper sound file in the aircraft's -set.xml file.
Has something to do with OpenAL not understanding where the sound comes from.
Has something to do with OpenAL not understanding the sound volume.
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?
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.
I use Autodesk 3ds Max (.3ds) occurs when the 3D data model.
Solution converts the file format AC3D.
This warning is generated from OSG. Set your environment variable
OSG_NOTIFY_LEVEL=FATAL
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.
Appears when printing large outputs (very) frequently on the screen.您还未登陆，请登录后操作！
登录时,忽然出现提示.是什么原因呀?
发送信息时,其它人会看到此信息,问是否发送,以前没有过这种情况的呀!(我是在家里上网),是不是中了木马病毒呀?请教高手该如何解决?
新装系统IE第一次操作都会出现，选过后就做为默认选项。以后都这么办了。这可以说只能同意。这就象tu_ping形容的一样告诉你一声外面的世界很危险。但是人总要出去的。就是提醒自己多加小心罢了。
问你是不是出去一样,因为出门可能会有不安全的事呢!你点选那个(下次不要再提示)就可以了,下次就不会出现了!
您的举报已经提交成功，我们将尽快处理，谢谢！
大家还关注