Jim Wilson writes: > On further investigation, it appears that this is almost certainly due to > normal variation in fdm position and orientation output. The variations are > probably correct, but the way 3D rendering works you get what appears to be a > jump when a pixel boundry is crossed. This is clearest when testing with the > magic carpet fdm. > > Maybe anti-aliasing would fix the problem, but it seems that the only > reasonable way to get rid of this is to make the cockpit a special case model > and overlay it after all the scenery, etc. is rendered (without the > position/orientation transformations). On the other hand I'm not sure that > this is a good idea as a perfectly stable cockpit that does not jitter at all > wouldn't be realistic either.
It seems strange that everything else in the cockpit and 3d model of the aircraft is perfectly stable and only this one instrument is jittery. Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
