20,741
edits
Troubleshooting crashes: Difference between revisions
Jump to navigation
Jump to search
→Introduction
| Line 16: | Line 16: | ||
I'd keep using the ufo until you have optimized all settings accordingly, i.e. don't touch the aircraft or location (airport, azimuth, offset) settings until you have really optimized everything else. | I'd keep using the ufo until you have optimized all settings accordingly, i.e. don't touch the aircraft or location (airport, azimuth, offset) settings until you have really optimized everything else. | ||
Also, please only touch the aircraft/location settings after having optimized everything else already, and after ensuring that you are getting good frame rates (>= 30 fps). Once you have done that, I'd suggest to look at aircraft with 2D panels - such as the c172p-2dpanel or other simple aircraft (TODO: list of aircraft with 2D panels). | Also, please only touch the aircraft/location settings after having optimized everything else already, and after ensuring that you are getting good frame rates (>= 30 fps). Basically, if you are not getting frame rates much higher than 100 fps with the "Level 0" startup profile, then using complex aircraft or scenery will be next to impossible with your system. | ||
Once you have done that, I'd suggest to look at aircraft with 2D panels - such as the c172p-2dpanel or other simple aircraft (TODO: list of aircraft with 2D panels). | |||
If you need help with the whole process, please get in touch via the FG forums. | If you need help with the whole process, please get in touch via the FG forums. | ||
| Line 29: | Line 31: | ||
Basically, the point of the following settings is to disable EVERYTHING that could have an effect on performance, to ensure that we get a working FlightGear window up and running with no eye candy at all, and maximum frame rate. | Basically, the point of the following settings is to disable EVERYTHING that could have an effect on performance, to ensure that we get a working FlightGear window up and running with no eye candy at all, and maximum frame rate. | ||
Once that is working, features can be re-enabled step by step. Features should only be re-enabled after evaluating their impact on performance, using the frame rate counter, frame spacing indicator, the built-in system monitor (can be inspected via telnet/http using --telnet5900) and the OSG on-screen stats. | Once that is working, features can be re-enabled step by step. Features should only be re-enabled after evaluating their impact on performance, using the frame rate counter, frame spacing indicator, the [[Howto:Use the system monitor|built-in system monitor]] (can be inspected via telnet/http using --telnet5900) and the OSG on-screen stats. | ||
Depending on the hardware specs of the target platform, adjusting the threading mode of FG/OSG may also help: [[Howto:Activate multi core and multi GPU support]]. | Depending on the hardware specs of the target platform, adjusting the threading mode of FG/OSG may also help: [[Howto:Activate multi core and multi GPU support]]. | ||