Jim Wilson wrote: > My guess is that the problem is that the output from the FDM's > jitters.
That's a possibility. One easy way to test this is to crash the A-4. When crashed, the FDM stops working and just repeats the same values forever. If the jitter stops, then this is the culprit. My intuition tells me that the problem is elsewhere, though. The jitter "feels" like a precision problem to me -- the polygons change shape ever so slightly, and you see what looks like a little z-fighting at their edges. That's not what you would expect from a simple rotation or translation of otherwise rigid geometry. Dunno; it's just a hunch. > I suspect that if we modified the location/viewer code to round the > orientation values to the nearest 1/100th degree we would see the > jitter go away. Not sure if there is a negative impact in doing > that. If the problem is in YASim, it should be fixed there. Re-interpreting broken values like this causes trouble, in my experience. Simply rounding isn't sufficient anyway, as you can still bounce/alias across the rounding boundaries. This would need to do something like low-pass filter the FDM output, which has other implications (it inserts a delay, for example). Actually, an intelligent filter that tried to model pilot head bobbing due to acceleration and orientation changes would be a really cool feature. So if this gets us on our way to that, I withdraw my objection. :) Andy -- Andrew J. Ross NextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
