Jon S. Berndt wrote: > The way we model them, using stability derivatives, we don't need to > as these things are wrapped up in the aero data itself. The > coefficients we get will be roll_moment_due_to_aileron_deflection, > pitch_moment_due_to_elevator_deflection, etc. and this data will > include the effects of motion of the pertinent aerosurface - > symmetrically deployed or not.
You've lost me. Specific example: An MU-2 pilot yanks the stick hard left. The spoiler deflection on the left wing goes to 1.0, and the right wing stays at zero. The FDM needs, somehow, to provide this information to the 3D model, no? Or are you expecting the 3D model code to figure it out on its own from the /control tree? Wasn't the point of moving to /surface-positions to put this intelligence into the FDM where it belongs? I think perhaps you haven't thought this through completely... 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
