On Sun, Jun 28, 2009 at 1:34 PM, Erik Hofman wrote: > I've seen something similar myself, but only when the sender sends the > data more frequently than FlightGear is allowed to handle with the > refresh parameter (60Hz in your example).
I haven't looked at the code, but generally, I think it makes sense (when dealing with live data) for the generic protocol to enter a while loop and read data until there is no more available. That way if the sender is sending at a higher rate or FlightGear gets behind for any reason, FlightGear will get caught up each iteration. This obviously does not work well for file input though, so you'd have to differentiate. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/
------------------------------------------------------------------------------
_______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
