20,741
edits
Troubleshooting crashes: Difference between revisions
Jump to navigation
Jump to search
→Minimal Startup Profile
| Line 44: | Line 44: | ||
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> | ||