Curtis L. Olson writes: > > > David Megginson writes: > > > > > Yes -- right now the surfaces are tied to /controls/* > > David, I'm starting to get nit-picky here :-) but one more thing > ... the elevator doesn't seem to be responding to elevator trim. In a > real life C172 the elevator trim is a little tab on the trailing edge > of the elevator that causes the elevator to actually change position > ... kind of like an elevator elevator.
You'll get this for free when the the model starts using FDM-reported control positions. Right now, /controls/elevator and /controls/elevator-trim are separate properties; they get summed only in the FDM. And on that subject, would you like to pick a property tree for the FDM output properties? How about "/control-positions"? Adding this support to YASim will be quick. Some things, though, might get a little complicated. On some aircraft (like the 172 Curt describes) trim is implemented as a mere offset to the control position. On others, though, it's a change to the incidence angle of the whole assembly. The MD-80 works this way; remember the crash due to the stripped jack screw? So distinct aircraft models will require special support from the FDM. There's no single "elevator" output that will work for all of them. In YASim, I think this can be made to work naturally by associating a given "output" property to each <control> entry. So you could make a dummy elevator-trim and elevator-flap control for the MD-80's output, while leaving the input elevator properties alone. 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
