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 13:59, 13 November 2016
, 13 November 2016→AI Traffic
(Switch to {{flightgear commit}}, {{flightgear url}}, and {{flightgear source}} to fix the broken Gitorious links. And OpenRTI has been switched from Gitorious to the current SourceForege repository via {{sourceforge source}}.) |
|||
| Line 243: | Line 243: | ||
== AI Traffic == | == AI Traffic == | ||
{{Main article|FGTraffic}} | |||
A simple [[Decoupling the AI Traffic System|AI model]] does just the trick what it does today. But more sophisticated modules might contain an own fdm so that these machines really live in the same fluid that the weather module provides data for.Note that the RTI API already provides a subscriber model that ensures that you don't feed data to participants that don't need that.May ba a radar controller screen that can be attached there to see the machines in this word. But sure that radar screen is not interested in flap animations for the aircraft ... | A simple [[Decoupling the AI Traffic System|AI model]] does just the trick what it does today. But more sophisticated modules might contain an own fdm so that these machines really live in the same fluid that the weather module provides data for.Note that the RTI API already provides a subscriber model that ensures that you don't feed data to participants that don't need that.May ba a radar controller screen that can be attached there to see the machines in this word. But sure that radar screen is not interested in flap animations for the aircraft ... | ||