On 02/25/2007 12:49 PM, Roy Vegard Ovesen wrote: > I have to agree with Dave on this. The indicated altitude should _not_ be > quantized. The indicated altitude "belongs" to the altimeter part of the > class, and _not_ to the encoder part.
Parts? I didn't know the class has an altimeter part separate from the encoder part. The class can be /configured/ to be one or the other. It cannot and should not be configured to be both. > AFAIK an encoder never outputs > indicated altitude. 1) We can agree that /usually/ the encoder does not put out indicated altitude. But there *are* backup altimeters that do display an indicated altitude derived from the encoder (quantization and all). This is not super-important. 2) The main reason for that feature was (a) because it was easy to do, and (b) to make life super-easy when writing autopilot code, so that the Kollsman shift could be calculated in one simple step, by subtraction. If the autopilot authors are not interested in doing that, they are requested to please ignore the indicated altitude output. Please don't complain about "bugs" in something that is both realistic and harmless. I've heard opinions, but I haven't heard any explanation of why quantizing the pressure altitude is either unrealistic *or* unhelpful. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
