Property Tree/Native Protocol Slaving: Difference between revisions

Property Tree/Native Protocol Slaving (view source)

765 bytes added , 26 March 2013

no edit summary

20,741

edits

@@ Line 4: / Line 4: @@
 In this case, depending on your command line options, FG can be configured to be a telnet server, an http server, a "dynamics" master/server, or a "dynamics" slave/client, and possibly some combination of all of those simultaneously depending on the context and what you are trying to accomplish.
+There is an --native-ctrls= command line option to send a set of flight control related properties.  It works just like the --native-fdm option,
+just remember to use a different port number.
+For past projects, I've used the --props= option to accept property configuration changes (things like weather effects and time of day.)  You
+can use this interface to read/write individual properties.  I setup a separate gui that was configured to know the ip addresses of all the slaves
+so it could update them appropriately when I wanted to make a change.  For the time of day, this presupposes that all the computer clocks are pretty
+closely in sync ... then you can send the same time offset to them (in seconds) so they all can display the same time of day effects.
 <pre>