option at all, FlightGear (since version 1.0) figures out the proper setting automatically. Note: for multiplayer, you don't need to use the -multiplay=in. When using multiplayer or socket input, this usually means you specified an invalid ip address or the port is in use. Another graphics card, or an older FlightGear version will likely 'fix' the problem.Įrror: bind() failed in make_server_socket() If that does not work, your graphics card is probably not able to run FlightGear 1.9 and higher. Try changing the BPP value of your FlightGear setup. If you are not the aircraft's author you can safely ignore such warnings.Įrror: GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified= xml file (where the animation is stored) to see if the object-names match those in the. This means that FlightGear is unable to find an object in a. You cannot use data from a different date than the binary's release date.Ĭould not find at least one of the following objects for animation: When using CVS with binaries, the data must match the binary.Set it using the -fg-root= commandline option. FlightGear was unable to find the $FG_ROOT directory.The message lets us know that TerraSync is updating the $FG_SCENERY/Airports directory.īase package check failed. 2.12 WARNING: PUI: Too many live puInterfaces open at once!.2.11 Warning: GraphicsWindowWin32::grabFocus() - Failed grabbing the focus.2.9 OpenAL error (AL_ILLEGAL_COMMAND): set_volume.2.8 OpenAL error (AL_ILLEGAL_COMMAND): set_source_pos.2.6 Nasal runtime error: stack overflow.2.5 Mesa 7.3 implementation error: bad texture level in r300UploadSubImage.2.4 FGMultiplayMgr::MP_ProcessData - message from.1.38 Warning: Picked up TriangleIntersect.1.37 WARNING: Couldn't convert texture.Possible cause: No such file or directory 1.36 Unknown exception to the main loop.1.35 Unexpected tag '.' found in YASim aircraft description.1.34 Unable to choose requested pixel format.1.33 Traffic manager could not find airport.1.31 The system cannot find the file specified.

1.30 ssgInit called without a valid OpenGL context.1.28 osgDB ac3d reader: detected surface with less than 3 vertices!.1.27 osgDB ac3d reader: could not find texture.1.26 OpenAL error (AL_INVALID_VALUE): constructor (alBufferData)Fatal error: Failed to buffer data.1.25 OpenAL error : bind source Failed to generate audio source.1.24 OBJECT_SIGN: unsupported glyph `.'.1.23 No render bin number specified in render bin section.

1.22 No render bin name specified in render bin section.

1.20 Nasal runtime error: nil used in numeric context.

doesn't seem to have routes associated with it

1.16 freeglut (fgfs): Unable to create direct context rendering for window 'FlightGear'This may hurt performance.

JSBSim failed to load aircraft and/or engine model

1.15 Found unexpected subsystem: system exiting.

1.14 FGPropertyManager::GetNode() No node found for.

1.13 FGMultiplayMgr - No receiver port, Multiplayermode disabled.

1.12 FGMultiplayMgr::MP_ProcessData: No such file or directory.

1.10 Fatal error: name must begin with alpha or '_'.

1.7 Error: RenderTexture requires the following unsupported OpenGL extensions.

1.6 Error: connect() failed in make_client_socket()SG_IO_OUT socket creation failed.1.5 Error: bind() failed in make_server_socket().1.4 Error: GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified=.1.3 Could not find at least one of the following objects for animation:.

Installing flightgear scenery