20,741
edits
Howto:Optimizing FlightGear for mobile devices: Difference between revisions
Jump to navigation
Jump to search
m
Howto:Optimizing FlightGear for mobile devices (view source)
Revision as of 09:01, 28 July 2012
, 28 July 2012→XML/Property Tree level optimizations
| Line 69: | Line 69: | ||
So, I'd suggest to customize your FG version accordingly and keep these settings disabled for starters. | So, I'd suggest to customize your FG version accordingly and keep these settings disabled for starters. | ||
There are probably a number of other opportunities to customize FG without touching the C++ code (even though optimizing the C++ code would definitely seem like a good idea in my opinion). Custom texture packs and custom-built scenery tiles were already mentioned. Making use of frame throttling and adjusting the FDM update interval (model-hz) would also seem to make sense. | There are probably a number of other opportunities to customize FG without touching the C++ code (even though optimizing the C++ code would definitely seem like a good idea in my opinion). Custom texture packs and custom-built scenery tiles were already mentioned. Making use of frame throttling and adjusting the FDM update interval (model-hz) would also seem to make sense. | ||
I didn't check the specs of the Android phones, but I'd also make sure to set up the threading mode properly. | I didn't check the specs of the Android phones, but I'd also make sure to set up the threading mode properly. | ||
In other words, even if you don't have access to an Android phone, there are certain things that can be done, and which would help (using an Android emulator via VirtualBox would be another option). Just customizing FG for limited targets like netbooks would also help, and if you have an old computer with an nvidia 6x/7x generation card, you could just as well try running FG. | In other words, even if you don't have access to an Android phone, there are certain things that can be done, and which would help (using an Android emulator via VirtualBox would be another option). Just customizing FG for limited targets like netbooks would also help, and if you have an old computer with an nvidia 6x/7x generation card, you could just as well try running FG. | ||
== Minimal Startup Profile == | |||
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: | |||
* --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=false | |||
* --disable-specular-highlight | |||
* --disable-ai-models | |||
* --disable-clouds | |||
* --disable-skyblend | |||
* --disable-textures | |||
* --fog-disable | |||
== OpenGL vs. OpenGL ES == | == OpenGL vs. OpenGL ES == | ||