20,741
edits
FlightGear high-level architecture support: Difference between revisions
Jump to navigation
Jump to search
FlightGear high-level architecture support (view source)
Revision as of 20:13, 25 April 2013
, 25 April 2013→Objective
No edit summary |
|||
| Line 15: | Line 15: | ||
= Objective = | = Objective = | ||
Document the ongoing HLA effort, to help people better understand how this affects a number of related FlightGear efforts and projects (particularly related to improved modularization, concurrency support and the [[Distributed Interactive Simulation|multiplayer]]/[[Decoupling the AI Traffic System|AI system]]). | Document the ongoing HLA effort, to help people better understand how this affects a number of related FlightGear efforts and projects (particularly related to [[Modularizing, parallelizing and distributing FlightGear|improved modularization, concurrency support]] and the [[Distributed Interactive Simulation|multiplayer]]/[[Decoupling the AI Traffic System|AI system]]). FlightGear related limitations have been extensively discussed over the years, for a comprehensive summary, please see [[Modularizing, parallelizing and distributing FlightGear]]. | ||
Although the FlightGear design fairly modular it's provided as a single binary. Everyone who wants to create a new I/O module must patch the FlightGear sources and compile the FlightGear binary from scratch. This may discourage those who want to use FlightGear as a tool and extend it in some way. Moreover, it's not always possible to include all functions in a single binary. Some functions may be mutually exclusive. | Although the FlightGear design fairly modular it's provided as a single binary. Everyone who wants to create a new I/O module must patch the FlightGear sources and compile the FlightGear binary from scratch. This may discourage those who want to use FlightGear as a tool and extend it in some way. Moreover, it's not always possible to include all functions in a single binary. Some functions may be mutually exclusive. | ||