John Wojnaroski wrote:
Thanks, that helps -- guess I'll dig around in the plib and Simgear code
Part of the question also relates to any penalty imposed on the FG frame
rate by adding multiple socket options for each IP address and unique port.
Any SWAG on the percentage for each additional socket? linear, geometric,
exponential? Or is it in the noise? Given that the current data packet is
about 700 bytes, the LAN is a long way from any performance limits, at least
for datagrams.
I don't have hard data, but my observation is that the network overhead is not much ... the biggest factor in getting good sync between all your machines is to have the all run at the same fixed, sustained frame rate. i.e. all your machines are locked at 60hz. If you master drops a frame, all your slaves will stutter. If a slave drops a frame, that is obviously a stutter. If the master is running at a different frame rate from any of the slaves, you will typically see some sort of jitter. If you are feeding FG from an external FDM, it's important to ensure that is feeding data at the same rate that FG is trying to render (which isn't always as simple as it might seem!) Just try and write a program on a stock unix box that does something at exactly 60hz, doesn't do anything related to graphics (thus can't depend on monitor sync), and doesn't use a busy-wait type loop for the timing (thus is cpu friendly.)
Let us know what you come up with on the broadcast stuff.
Regards,
Curt.
-- Curtis Olson http://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
