> Here is what I'm going to do: > - change gs-needle-deflection to report the GS deviation *in degrees* > - add a gs-needle-deflection-norm property, reporting the > deflection as the range +/- 1.0 (I'll probably do that for the CDI as > well). 1.0 will be on the peg, 0.0 will be centred - no surprises > here, I hope. > - clamp the GS deviation to +/- 0.7 degrees in the nav-radio code (as > we clamp the CDI deflection to +/-10 degrees). This is significant, > because many panels currently work due to the value *not* being > clamped to any range. I.e there will be a peg at the sim level, not > just a a peg defined at the animation / panel level. Hi James
I really appreciate your work on this topic! I don't think clamping the deviation to +/-0.7 degrees and the normalized value to +/- 1.0 is a good idea. Instruments like the KI525 HSI move the glide slope needle out of sight when the glideslope signal is not valid or you are way above or below glideslope. If you clamp the values, this information is lost for the instrument. Cheers, Torsten ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
