Howto:Understand console output: Difference between revisions

Jump to navigation Jump to search
m
+ a couple of more errors and solutions
m (+ new error)
m (+ a couple of more errors and solutions)
Line 4: Line 4:


==Errors with known 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 146: Line 146:
===Unable to choose requested pixel format===
===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.
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===
===Unable to open aircraft directory===
Line 168: Line 173:
===Warning: TangentSpaceGenerator: unknown primitive mode 9===
===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.
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===
===YASim SOLUTION FAILURE:<br>Zero length fuselage===
Line 176: Line 184:


===AL Error (fx): Invalid Value at pitch and gain===
===AL Error (fx): Invalid Value at pitch and gain===
===AL Error (sound manager): Invalid Operation at update===


===AL Error (sound manager): Invalid Value at buffer add data<br>No such buffer!===
===AL Error (sound manager): Invalid Value at buffer add data<br>No such buffer!===

Navigation menu