20,741
edits
FlightGear run levels: Difference between revisions
Jump to navigation
Jump to search
→Problem
| Line 34: | Line 34: | ||
== Problem == | == Problem == | ||
[[File:Dedicated-aircraft-subsystem-group-for-fgcanvas.png|600px|thumb|checking how difficult it would be to put all aircraft related subsystems (fdm, replay, history, controls etc) into a single SGSubsystemGroup named "main-aircraft" to easily make the whole shebang optional using a single --prop for "FGCanvas" use, but also to check if it's feasible to prepare things for later reuse by the AI traffic system (for AI traffic that uses actual FDMs, APs and RMs - but also so that things are affected by the environment) , and it's actually working - even though reset/re-init is obviously hard-coded currently, which I am breaking by shuffling around subsystems, but as long as each SGSubsystemGroup implements the full SGSubsystem interface (postinit, reinit, shutdown etc), this could help clean up fg_init.cxx quite considerably [http://forum.flightgear.org/viewtopic.php?f=71&t=23499]]] | |||
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 not always required and their initialization should be optional, | 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 not always required and their initialization should be optional, | ||