--- Erik Hofman <[EMAIL PROTECTED]> wrote: > Andy Ross wrote: > > Erik Hofman wrote: > > > Well It's making it slightly difficult for the > sound code. But I saw > > > YASim does the same. > > > > These numbers are actually generated by the panel > code, not the FDM. > > Both FDMs just seek the position to the specified > control input. In > > this case, the panel code adds or subtracts 0.33 > to the current value. > > You're seeing the rounding error resulting from > the > > not-quite-one-third stepping value. Add some > threes. :) > > > We're starting to create a problem here. > There are different values for keyboard, mouse > (panel) and IO modules. > > I think we should define a fixed value for each flap > position, otherwise > every module looking at the value has to support (>0 > && <0.32 or >0.34 > && <0.66 or >0.66 && <1.0)!
Making the sound code dependent upon particular values of flap position might not be a good idea. Many aircraft have a different number of flap detents, some as many as nine. I would suggest that the controlling code generate an "in-transit" flag or, conversely, an "in-detent" flag. > > Erik > > > > > _______________________________________________ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > > __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/ _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
