On the Seneca II model, the KX 165 radios are broken. -- When I try to tune 116.0 I get 116.99 -- When I try to tune 111.7 I get 111.69 -- But you can't just say everything is off by 0.01 MHz, because if I put in 116.01, I get 116.01. The 116.0 result is skipped, i.e. avoided!
I imagine that somewhere in the backend somebody is doing a floor() when they should be doing a round(). Or some such. Unless somebody has a better idea, I will add this report to the wiki: http://wiki.flightgear.org/flightgear_wiki/index.php?title=Piper_PA34-200T_Seneca_II within the next day or so. 1) This is using fsgs compiled from a very recent cvs. Also using a very recent data/ tree. 2) The same bug (plus additional weirdness) is observed using the fgfs binary as distributed back in May. ------------------------------------------------------------------------- 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
