20,741
edits
Property Tree/Native Protocol Slaving: Difference between revisions
Jump to navigation
Jump to search
Property Tree/Native Protocol Slaving (view source)
Revision as of 19:07, 26 March 2013
, 26 March 2013no edit summary
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
There is no synchronization in the native-fdm and native-ctrls protocols used for multiple displays. The master instance just transmit to the slaves, who process the data when and in the order it is received. This ought to work without problems in a local network. | There is no synchronization in the native-fdm and native-ctrls protocols used for multiple displays. The master instance just transmit to the slaves, who process the data when and in the order it is received. This ought to work without problems in a local network. | ||
It might not be a good idea to throttle the frame rate to the data rate - FG will only check for input (at most) once per frame and that could easily fall out of sync with the producer in this case (if data arrives too late in some frames). If FG consumes all pending data it finds that could explain the jerks. Can you try throttling to 2x the data rate? | |||
<pre> | <pre> | ||
//*** example to slave one copy of fgfs to another *** | //*** example to slave one copy of fgfs to another *** | ||