FlightGear high-level architecture support: Difference between revisions

FlightGear high-level architecture support (view source)

1,261 bytes added , 19 November 2015

20,741

edits

@@ Line 65: / Line 65: @@
    }}
 }}
+{{FGCquote
+|1= I'm planning to use an IEEE 1516 standard RTI, of which OpenRTI is a conveniently free implementation. AFAICT this is one of the main standards for distributed simulation communication (the other being DIS). I think that will address the communications side of the equation, and OpenRTI can work both as a local RTI and over a network. It's also got a robust logical time implementation, and the ability to clock the simulation.
+|2= {{cite web
+  | url    = http://sourceforge.net/p/flightgear/mailman/message/34632142/
+  | title  = <nowiki>Re: [Flightgear-devel] HLA developments</nowiki>
+  | author = <nowiki>Stuart Buchanan</nowiki>
+  | date   = Nov 19th, 2015
+  }}
+}}
+{{FGCquote
+|1= In terms of integration with the property tree, I'm thinking that in the short term all the different components that we split out into separate threads or executables will simply use their own properties trees, and use the RTI to reflect the particular (minimal) data that needs to be passed between components.
+|2= {{cite web
+  | url    = http://sourceforge.net/p/flightgear/mailman/message/34632142/
+  | title  = <nowiki>Re: [Flightgear-devel] HLA developments</nowiki>
+  | author = <nowiki>Stuart Buchanan</nowiki>
+  | date   = Nov 19th, 2015
+  }}
+}}
 {{FGCquote