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:30, 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. 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) and the OSG on-screen stats. | 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. 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) and the OSG on-screen stats. | ||
Depending on the hardware specs, 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=270 | |||
* --altitude=500 | |||
* --model-hz=60 | * --model-hz=60 | ||
* --bpp=16 | * --bpp=16 | ||