20,741
edits
Troubleshooting crashes: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Created page with " If FlightGear crashes, it's possible that this is due a number of reasons, such as limited hardware resources (CPU, GPU, RAM etc) - so crashes are not necessarily due to a fa...") |
No edit summary |
||
| Line 1: | Line 1: | ||
== Introduction == | |||
If FlightGear crashes, it's possible that this is due a number of reasons, such as limited hardware resources (CPU, GPU, RAM etc) - so crashes are not necessarily due to a faulty program. | If FlightGear crashes, it's possible that this is due a number of reasons, such as limited hardware resources (CPU, GPU, RAM etc) - so crashes are not necessarily due to a faulty program. | ||
| Line 24: | Line 25: | ||
* error messages and warnings (console output) | * error messages and warnings (console output) | ||
* screen shots | * screen shots | ||
=== Minimal Startup Profile: Level 0 === | |||
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. | |||
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]]. | |||
* --airport=ksfo | |||
* --offset-distance=4000 | |||
* --offset-azimuth=90 | |||
* --altitude=500 | |||
* --heading=0 | |||
* --model-hz=60 | |||
* --bpp=16 | |||
* --enable-wireframe | |||
* --disable-random-objects | |||
* --prop:/sim/rendering/quality-level=0 | |||
* --prop:/sim/rendering/shaders/quality-level=0 | |||
* --disable-ai-traffic | |||
* --prop:/sim/ai/enabled=0 | |||
* --aircraft=ufo | |||
* --disable-sound | |||
* --prop:/sim/rendering/random-vegetation=0 | |||
* --prop:/sim/rendering/random-buildings=0 | |||
* --disable-specular-highlight | |||
* --disable-ai-models | |||
* --disable-clouds | |||
* --disable-clouds3d | |||
* --disable-skyblend | |||
* --disable-textures | |||
* --fog-fastest | |||
* --visibility=5000 | |||
* --disable-distance-attenuation | |||
* --disable-enhanced-lighting | |||
* --disable-skyblend | |||
* --disable-textures | |||
* --disable-real-weather-fetch | |||
Using these settings, I am getting frame rates between 400-500 fps and a steady frame spacing (latency) of 3-11 ms, on a notebook from 2007 (1024x768). Disabling wireframe mode lowers the framerate by about 50-80 fps. | |||
[[File:Fgfs28-bare-bones.png|thumb 200px|FlightGear bare bones]] | |||
As can be seen, additional resources can be freed by flying in areas without scenery (ocean tiles), and by using simple aircraft like the ufo. And by using a HUD instead of a 2D/3D cockpit panel. | |||