John Wojnaroski writes: > Just uploaded the latest FG 09.3 -- quite a step from 0.7.9 !! > > When setting up multiple machines on a network what are the new command line > parameters to connect master and slave FG machines to generate multiple > external views? > > Which protocol should one use? 'native-ctrls=' or 'native-fdm=' or 'native=' > ? > Did a portion of the howto docs on using and specifying the network > parameters get lost?
The two protocols compliment each other. Originally they were designed to communicate with an external FDM. FlightGear would send native-ctrls to the remote FDM module, and it would reply with native-fdm data. You can sync up visuals by only using native-fdm= since that contains all the position and orientation information. If you also want to syncronize the control inputs (i.e. for animating the external model) you can add that. This comes in really handy if you are running the wright flyer on a 5 projector wrap around visual system. You want to see that big elevator waggling in front of you as you struggle to stay alive for just a few more seconds. > Should the slaves specify --fdm=external or --fdm=null? The slaves should use --fdm=null so they don't try to compute their own positional information. Regards, Curt. -- Curtis Olson HumanFIRST Program FlightGear Project Twin Cities curt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.flightgear.org/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
