20,741
edits
Howto:Optimizing FlightGear for mobile devices: Difference between revisions
Jump to navigation
Jump to search
Howto:Optimizing FlightGear for mobile devices (view source)
Revision as of 09:15, 28 July 2012
, 28 July 2012→Minimal Startup Profile
| Line 78: | Line 78: | ||
Basically, the point of the following setting is to disable EVERYTHING that could have an effect on performance, to ensure that we get a working FlightGear window up and running. Once that is working, features can be re-enabled step by step: | Basically, the point of the following setting is to disable EVERYTHING that could have an effect on performance, to ensure that we get a working FlightGear window up and running. Once that is working, features can be re-enabled step by step: | ||
* --model-hz | |||
* --bpp=16 | * --bpp=16 | ||
* --enable-wireframe | * --enable-wireframe | ||
| Line 97: | Line 98: | ||
Additional resources can be freed by flying in areas without scenery (ocean tiles), and by using simple aircraft like the ufo. In addition, custom texture packs may help to reduce the memory footprint. Further memory savings can be achieved by reducing the size of the NavDB in $FG_ROOT | Additional resources can be freed by flying in areas without scenery (ocean tiles), and by using simple aircraft like the ufo. In addition, custom texture packs may help to reduce the memory footprint. Further memory savings can be achieved by reducing the size of the NavDB in $FG_ROOT | ||
Also, it helps not to use subsystems like instruments and/or the autopilot system, by not loading the via the aircraft-set.xml | |||
== OpenGL vs. OpenGL ES == | == OpenGL vs. OpenGL ES == | ||