20,741
edits
Howto:Reset/re-init Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
m
Howto:Reset/re-init Troubleshooting (view source)
Revision as of 18:21, 27 January 2016
, 27 January 2016→Objective
m (→Objective: add pointers from related wiki articles: FDM_engine_feature_standardization, Recommended_Property_Tree_Enhancements, Modularizing,_parallelizing_and_distributing_FlightGear) |
m (→Objective) |
||
| Line 24: | Line 24: | ||
The core developers are aiming to find out the dependencies of different subsystems<ref>http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg18066.html</ref>, and re-factor them so that more and more subsystems can be made optional (analogous to [[FlightGear Run Levels|run-levels]])<ref>http://forum.flightgear.org/</ref>, enabling them to be dynamically removed and re-added at run-time. This will be particularly important to untangle implicit or hard-coded dependencies among the different subsystems, and will be one of the key tasks to move certain subsystems into dedicated [[High-Level Architecture]] (HLA) {{wikipedia|High-level architecture#Common HLA terminology|federates|noicon=1}}. | The core developers are aiming to find out the dependencies of different subsystems<ref>http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg18066.html</ref>, and re-factor them so that more and more subsystems can be made optional (analogous to [[FlightGear Run Levels|run-levels]])<ref>http://forum.flightgear.org/</ref>, enabling them to be dynamically removed and re-added at run-time. This will be particularly important to untangle implicit or hard-coded dependencies among the different subsystems, and will be one of the key tasks to move certain subsystems into dedicated [[High-Level Architecture]] (HLA) {{wikipedia|High-level architecture#Common HLA terminology|federates|noicon=1}}. | ||
One of the long-term goals is to provide a so called "[[FlightGear Headless|headless]]" mode so that certain features/subsystems (unrelated to graphics) can be better tested in isolation. An example would running FlightGear in an automated fashion on the [[FlightGear Build Server]], which could help increasingly automate the release process and related regression testing. | One of the long-term goals is to provide a so called "[[FlightGear Headless|headless]]" mode so that certain features/subsystems (unrelated to graphics) can be better tested in isolation. An example would running FlightGear in an automated fashion on the [[FlightGear Build Server]], which could help increasingly automate the release process and related regression testing<ref>http://sourceforge.net/p/flightgear/mailman/message/34741767/</ref>. | ||
The other goal is to increasingly modularize FlightGear by using HLA and split off the simulation loops (see also [[FGViewer]]), as well as [[Supporting multiple renderers|supporting different renderers]] (such as [[Rembrandt]] and [[ALS]]), scenery engines (e.g., standard and [[osgEarth]]) and weather engines, in a fashion similar to how FlightGear already supports different FDM engines ([[JSBSim]] and [[YASim]]). HLA will make it possible for certain subsystems to be moved to dedicated cores by using separate threads or even processes, meaning that certain subsystems may even be able to be on a different computer, in a distributed setup. | The other goal is to increasingly modularize FlightGear by using HLA and split off the simulation loops (see also [[FGViewer]]), as well as [[Supporting multiple renderers|supporting different renderers]] (such as [[Rembrandt]] and [[ALS]]), scenery engines (e.g., standard and [[osgEarth]]) and weather engines, in a fashion similar to how FlightGear already supports different FDM engines ([[JSBSim]] and [[YASim]]). HLA will make it possible for certain subsystems to be moved to dedicated cores by using separate threads or even processes, meaning that certain subsystems may even be able to be on a different computer, in a distributed setup. | ||