Norman Vine <[EMAIL PROTECTED]> said: > Since these routines only run once or twice per iteration of the loop > They really don't have to be 'super optimized' and I think my method > of handling them as 3x3 and just filling in the 4th row and column > by 'inspection' is probably good enough. > Yes that's what I was noticing. What I was speculating is that there might be a way to consolidate by either passing a Vec3 or Vec4 as a parameter, but to be honest I haven't taken the time to compare the details of the various matrix functions. Probably what your doing is most efficient!
> That said I am all for separating the math from the properties interface as > much as possible and I think that we could probably create a 'number > crunching core' SimGear 'Viewer' that was passed only numbers from the > FlightGear 'Viewer' that provided the properties Interface to FGFS > Makes sense. It might want to be called ViewMath or something like that. It's got to go somewhere so that models can maintain their own position and rotation data (I mean for the model body itself, not the animations that are already there). Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
