Erik Hofman wrote: > I tried this with a linear interpolation table but I think a problem > right now is the fact that the timer is frame rate dependent. And > since I'm running at a frame rate of about 5 frames per second this > can be a problem.
The interpolator is realtime (er, simtime) based; frame rate doesn't effect it. It runs only once per frame, but the property changes it manages are based on actual time deltas. The 5Hz update will affect the granularity of settimer() calls, but over 10 seconds the error is negligible. You might see a "skip" once every 10 seconds as the timer resets. Even that can be hidden by removing the first two arguments of the interpolate call (which set the value by "interpolating" over a zero time delta) and initializing the property somewhere else. Andy _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
