20,741
edits
Troubleshooting crashes: Difference between revisions
Jump to navigation
Jump to search
→Introduction
No edit summary |
|||
| Line 5: | Line 5: | ||
It's just as well possible that the FlightGear default settings are not supported with your hardware/drivers, so that the process will be killed by the OS because it's trying to do something not supported by your computer. If you are experiencing full system crashes, you should see [[System Crashes]] instead. | It's just as well possible that the FlightGear default settings are not supported with your hardware/drivers, so that the process will be killed by the OS because it's trying to do something not supported by your computer. If you are experiencing full system crashes, you should see [[System Crashes]] instead. | ||
By default, FlightGear 2.6+ will assume a certain runtime environment and certain GPU features which may not be suppported by most older cards, such as GeForce 6/7 generation hardware and most older hardware (older than say 4-5 years), so that it can be expected that FG will not work on such computers "out of the box", i.e. the default startup settings will need to be customized accordingly, to disable all unsupported default features. See [[Hardware Recommendations]] for more details. | By default, FlightGear 2.6+ will assume a certain runtime environment and certain GPU features which may not be suppported by most older cards (e.g. shader support), such as GeForce 6/7 generation hardware and most older hardware (older than say 4-5 years), so that it can be expected that FG will probably not work on such computers "out of the box" and may get terminated by your operating system eventually, i.e. the default startup settings will need to be customized accordingly, to disable all unsupported default features. See [[Hardware Recommendations]] for more details. | ||
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 raise the FlightGear log level, so that you get to see where the program stops starting/working [http://wiki.flightgear.org/Howto:Improve_framerates#Debugging.2Flog_level]. | 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 raise the FlightGear log level, so that you get to see where the program stops starting/working [http://wiki.flightgear.org/Howto:Improve_framerates#Debugging.2Flog_level]. | ||