20,741
edits
FlightGear run levels: Difference between revisions
Jump to navigation
Jump to search
→Problem
| Line 32: | Line 32: | ||
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. | 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 "viewer", or a [[FGPanel]]/[[FGCanvas]] mode or a standalone ATC client, requires some refactoring in order to make subsystem initialization optional and fully runtime-configurable. | In other words, to reuse the FlightGear binary for other purposes, such as a standalone "viewer" (see [[FGViewer]], or a [[FGPanel]]/[[FGCanvas]] mode or a standalone ATC client, requires some refactoring in order to make subsystem initialization optional and fully runtime-configurable. | ||
Also, this work should align well with other currently ongoing plans, such as for example decoupling the viewer from the rest of the simulation loop: | Also, this work should align well with other currently ongoing plans, such as for example decoupling the viewer from the rest of the simulation loop: | ||