8,827
edits
Howto:Understand console output: Difference between revisions
Jump to navigation
Jump to search
m
Two errors added, of which one without known solution.
m (+ another error and solution) |
m (Two errors added, of which one without known solution.) |
||
| Line 1: | Line 1: | ||
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 [[FlightGear Launch Control#Debugging|Log Level]]. | 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 [[FlightGear Launch Control#Debugging|Log Level]]. | ||
==Errors with solutions== | ==Errors with known solutions== | ||
===Airports/.... Done=== | ===Airports/.... Done=== | ||
This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG_SCENERY]]/Airports</tt> directory. | This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG_SCENERY]]/Airports</tt> directory. | ||
| Line 129: | Line 129: | ||
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. | 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. | ||
==Errors without solutions== | ===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. | |||
==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 grealy appreciated! | 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! | ||
| Line 140: | Line 143: | ||
===FGMultiplayMgr::MP_ProcessData - message from ... has invalid length!=== | ===FGMultiplayMgr::MP_ProcessData - message from ... has invalid length!=== | ||
===GPS: malformed route, index=1=== | |||
===Mesa 7.3 implementation error: bad texture level in r300UploadSubImage=== | ===Mesa 7.3 implementation error: bad texture level in r300UploadSubImage=== | ||