573
edits
Troubleshooting crashes: Difference between revisions
Jump to navigation
Jump to search
m
link update
m (section moved to Troubleshooting performance issues#For the geeks out there) |
m (link update) |
||
| Line 29: | Line 29: | ||
== Running FlightGear with minimal settings == | == Running FlightGear with minimal settings == | ||
In such cases, it is important to start up FlightGear with minimum settings, and start re-enabling features step by step to see what settings are supported by your hardware. You may want to [[ | In such cases, it is important to start up FlightGear with minimum settings, and start re-enabling features step by step to see what settings are supported by your hardware. You may want to [[Flightgear debug log|raise the FlightGear log level]], so that you get to see where the program stops starting/working, and what it was doing before it got terminated. | ||
The following settings are really just intended to provide a '''minimal startup profile''', with ALL eye candy disabled by default - so that FG doesn't crash due to lack of certain features (OpenGL, shaders etc) and you get a "bare bone" FlightGear window. They use the UFO, as it is the least complex aircraft (the default aircraft is the Cessna 172) and a suitable scenery location to rule out aircraft or scenery as a cause for crashes. | The following settings are really just intended to provide a '''minimal startup profile''', with ALL eye candy disabled by default - so that FG doesn't crash due to lack of certain features (OpenGL, shaders etc) and you get a "bare bone" FlightGear window. They use the UFO, as it is the least complex aircraft (the default aircraft is the Cessna 172) and a suitable scenery location to rule out aircraft or scenery as a cause for crashes. | ||