Howto:Optimizing FlightGear for mobile devices: Difference between revisions

Howto:Optimizing FlightGear for mobile devices (view source)

225 bytes added , 28 July 2012

20,741

edits

@@ Line 138: / Line 138: @@
 Obviously, you will need to be able to build FG from source, probably using a cross compiler.
-But if you know C++, and especially OpenGL/OSG, you could definitely optimize FlightGear such that it's less resource hungry.
+Ideally, you would be familiar with using Virtualization (e.g via VirtualBox or VMWare) or emulators, so that you can actually run the binaries yourself. Obviously, having access to real hardware would be just as good.
+So if you know C++, and especially OpenGL/OSG, you could definitely help optimize FlightGear such that it's less resource hungry.
 As was said in the Android thread, there are a number of resource-hungry subsystems that could be simply disabled individually, such as the AI traffic system, or shader support.
-Being able to disable subsystems individually will be great for the whole simulator, not just for this effort: [[FlightGear Run Levels]].
+Being able to disable subsystems individually will be useful for the whole simulator, not just for this effort: [[FlightGear Run Levels]].
 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.