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 07:06, 28 July 2012
, 28 July 2012→Approach
m (→Problem) |
m (→Approach) |
||
| Line 52: | Line 52: | ||
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. | ||
== OpenGL vs. OpenGL ES == | |||
If FG could be made to run with opengl es, it could potentially run on mobile devices that support it and have high enough resources, so long as the rest of the FDM, terrain, and models would work too. However, how to compile the code would depend on the OS, and it seems the iphone uses a cut-down embedded version of OS X. Regular FG can work with regular OS X, so it seems plausible that it could be compiled for the modified OSX (maybe the iphone sdk would help here). | |||
I have hope this is possible if we can find somone with more expertise in programming. I mean, we know FG can run on OS X, and that it needs Open GL. The iphone can use OpenGl ES and seems to use a cut down OS X. | |||
If the differences between them can be over come, then it would be a matter of getting FG system requirements low enough. There is enough hard drive space for even the full version, so its a matter of running it (if the software issues can be overcome). 128 mb memory and the processor seems low, but rendering hvga or qvga is less demanding too. | |||
== Approach == | == Approach == | ||
| Line 65: | Line 71: | ||
Being able to disable subsystems individually will be great for the whole simulator, not just for this effort: http://wiki.flightgear.org/FlightGear_Run_Levels | Being able to disable subsystems individually will be great for the whole simulator, not just for this effort: http://wiki.flightgear.org/FlightGear_Run_Levels | ||
== Related == | == Related == | ||