Erik Hofman wrote:
 > Andy Ross wrote:
 > > Would it help for the FDM to supply a "moving" flag in the property
 > > tree?  This actually seems like it would be easier to do by
 > > comparing with a per-sound "last" value in the sound code, though.
 >
 > I've not seen any situation which might need it.

Sure you have.  On a real 172, moving the flaps lever from 0 to 30
causes the flap motors to whine for 5 seconds (or whatever).  Moving
it from 0 to 10 causes only 2 seconds of whine.  Moving it from 30 to
20 lasts for 4 seconds...

In the current code, you get 7 seconds* of whine, period, no matter
how far the deflection was.  If you make a small change to the flaps
while watching the wings, the 3D flaps will stop moving long before
the sound stops.

My point was that now that we know the "true" deflections of the
control surfaces the sound code can use this information to be
intelligent about when to stop playing the loop, and that this would
be a Good Thing.

Andy

* Or thereabouts.  The length of the audio sample.

-- 
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

Reply via email to