Howto:Optimizing FlightGear for mobile devices: Difference between revisions

There are many other subsystems which are started by default and which cannot be currently disabled, so more CPU/RAM resources can be saved by editing [https://gitorious.org/fg/flightgear/blobs/next/src/Main/fg_init.cxx#line1043 $FG_SRC/Main/fg_init.cxx] and by making more subsystems optional there, using a property to decide if the subsystem shall be started or not.

 

 

While disabling these systems can be fairly easily accomplished using ifdefs, care must be taken that FlightGear still builds properly and that no other systems are trying to access disabled subsystems, so this will involve repeated edit/build/debugging sessions using gdb.

Preparing FlightGear to be run on mobile platforms will take some heavy customizations, not just at the XML/property tree level, but also the source code level.

That being said, it would make sense for people to team up with other FlightGear users who are interested in running FlightGear on such devices (mobile phones, netbooks, game consoles), if you manage to cooperate, you could actually make this work, regardless of your target platform - simply because these customizations will be useful for all such efforts.  

Because they are first of all about reducing the FlightGear resource footprint (CPU, GPU, RAM, disk space), but also targeting FlightGear for devices which may not have a real screen, or keyboard/mouse support will be necessary. In addition, custom scenery/aircraft packs, with customized textures or rebuilding scenery via TerraGear may help.