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 14:06, 26 April 2013
, 26 April 2013→Benefits
| Line 117: | Line 117: | ||
The communications infrastructure based on RTI provides a huge potential to split the simulation into components that run on different cores or even machines but still being tight coupled. | The communications infrastructure based on RTI provides a huge potential to split the simulation into components that run on different cores or even machines but still being tight coupled. | ||
Major benefits would be to move some code, such as the | Major benefits would be to move some code, such as the [[Decoupling the AI Traffic System|AI code out of the main loop]] - may be even | ||
into a seperate process/thread. Also runnig one instance of | into a seperate process/thread. Also runnig one instance of that [[Decoupling the AI Traffic System|AI traffic]] for installations like we used to have at the linux tag booth would be a major advantage there. | ||
Anyway, I also consider an RTI a possible multiplayer replacement. Even if we would handle local RTI federations different than internet wide stuff. But yes, an RTI provides almost all we would need to get that right. | Anyway, I also consider an RTI a possible multiplayer replacement. Even if we would handle local RTI federations different than internet wide stuff. But yes, an RTI provides almost all we would need to get that right. | ||