Troubleshooting crashes: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 1: Line 1:
<font color="red">'''Note:''' FlightGear 2.10 users seeing crashes during simulator startup (without seeing the actual aircraft/scenery) with very old graphics cards that lack GLSL (shader) support should know that there used to be a bug in 2.10 that broke support for graphics cards without any shader support. In other words, if you are able to run other OpenGL software, but cannot even display the about dialog in FG 2.10 using the minimal startup profile detailed below, it is almost certainly your graphics card's lack of shader support causing the issue, because FlightGear 2.10 tries to copy graphics card information to the property tree for debugging purposes, to allow end-users to provide better troubleshooting reports - ironically, this very feature introduced crashes for all 2.10 users without any GLSL support. This issue has been fixed in FlightGear 2.11+ </font>


If FlightGear crashes (or looks/performs very badly), it's possible that this is due a number of reasons, such as limited hardware resources (CPU, GPU, RAM etc) or insufficient driver support - so crashes are not necessarily due to a faulty program. Also see [[FlightGear Benchmark]].
If FlightGear crashes (or looks/performs very badly), it's possible that this is due a number of reasons, such as limited hardware resources (CPU, GPU, RAM etc) or insufficient driver support - so crashes are not necessarily due to a faulty program. Also see [[FlightGear Benchmark]].
Line 45: Line 47:
You can directly use a custom [[Fgfsrc]] file for the following sections or parse the following lines to the console (separated by one empty character) after "FGFS" or set the respective options in [[Fgrun]] or in [[FlightGear configuration via XML|one of FlightGear's XML configuration files]].  
You can directly use a custom [[Fgfsrc]] file for the following sections or parse the following lines to the console (separated by one empty character) after "FGFS" or set the respective options in [[Fgrun]] or in [[FlightGear configuration via XML|one of FlightGear's XML configuration files]].  


'''Note:''' People seeing crashes while using FlightGear 2.10 with very old graphics cards that lack GLSL (shader) support should know that there used to be a bug in 2.10 that broke support for graphics cards without shader support. In other words if you are able to run other OpenGL software, but cannot even display the about dialog using the startup profile, it is almost certainly your graphics card's lack of shader support causing the issue, because FlightGear 2.10 tries to copy graphics card information to the property tree for debugging purposes. This issue has been fixed in FlightGear 2.11+


<pre>
<pre>

Navigation menu