20,741
edits
FlightGear run levels: Difference between revisions
Jump to navigation
Jump to search
→Update 08/2012
| Line 4: | Line 4: | ||
== Update 08/2012 == | == Update 08/2012 == | ||
This is currently being worked on as part of the [[Flightgear On Android]] project. | This is currently being worked on as part of the [[Flightgear On Android]] project. | ||
== Problem == | |||
FlightGear has a number of subsystems which cannot currently be disabled, so that they are always running because their initialization is entirely hard-coded. However, many of these systems are conceptually not required and their initialization should be optional, | |||
On the one hand, running subsystems which are not required may eat up computing resources that could be better used for different purposes/subsystems (i.e. to improve the frame rate), on the other hand - it is becoming increasingly difficult to reset and re-initialize the simulator properly, due to the number of subsystems which cannot be easily restarted. | |||
Also, it is currently next to impossible to use FlightGear for purposes other than the primary purpose, i.e. "simulation", because the FlightGear initialization code works such that it always assumes that there's a full simulator running, including ALL the subsystems like FDM, autopilot, sound, scenery etc. | |||
In other words, to reuse the FlightGear binary for other purposes, such as a standalone [[FGPanel]]/[[FGCanvas]] mode or a standalone ATC client, requires some refactoring in order to make subsystem initialization optional and fully runtime-configurable. | |||
== Background == | == Background == | ||