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 21:43, 21 November 2015
, 21 November 2015→Objective
m (→Nasal example: remove redundant leftovers from early prototype) |
m (→Objective) |
||
| Line 27: | Line 27: | ||
The other goal here being to increasingly modularize FlightGear by using [[HLA]] (high-level architecture), and splitting off the simulation/rendering loops (see [[FGViewer]]), as well as [[Supporting multiple renderers]] (think Rembrandt/ALS), and scenery engines (standard and osgEarth), analogous to how FlightGear already supports different FDM engines (JSBSim and YASim), but also different weather engines and rendering engines (standard/Rembrandt, ALS). HLA will make it possible for certain subsystems to be moved to dedicated cores by using separate threads or even processes, which also means that certain subsystems may even be running on a different computer, in a distributed setup. | The other goal here being to increasingly modularize FlightGear by using [[HLA]] (high-level architecture), and splitting off the simulation/rendering loops (see [[FGViewer]]), as well as [[Supporting multiple renderers]] (think Rembrandt/ALS), and scenery engines (standard and osgEarth), analogous to how FlightGear already supports different FDM engines (JSBSim and YASim), but also different weather engines and rendering engines (standard/Rembrandt, ALS). HLA will make it possible for certain subsystems to be moved to dedicated cores by using separate threads or even processes, which also means that certain subsystems may even be running on a different computer, in a distributed setup. | ||
The underlying requirement that these efforts share is that there needs to be a much better re-/initialization process, so that there are no hard-coded assumptions about running subsystems or initialization order. | The underlying requirement that all these efforts share is that there needs to be a much better re-/initialization process, so that there are no hard-coded assumptions about running subsystems or initialization order. | ||
In fact, many of these efforts are basically blocked by [[Reset/re-init]], or at the very least, fixing up [[Reset/re-init]] will greatly simplify overlapping efforts. | |||
For the time being, many of these efforts are not yet completely functional, so more feedback and data are needed. | For the time being, many of these efforts are not yet completely functional, so more feedback and data are needed. | ||