> 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. That's a known bug and I have no Idea how to get rid of it.Have been digging into the source and no result (yet). As a workaround, I added this to my .fgfsrc
--prop:/instrumentation/comm/frequencies/selected-mhz=126.8501 --prop:/instrumentation/comm/frequencies/standby-mhz=124.2201 --prop:/instrumentation/comm[1]/frequencies/selected-mhz=121.8001 --prop:/instrumentation/comm[1]/frequencies/standby-mhz=132.1201 --prop:/instrumentation/nav/frequencies/selected-mhz=111.5001 --prop:/instrumentation/nav/frequencies/standby-mhz=113.1001 --prop:/instrumentation/nav[1]/frequencies/selected-mhz=113.1001 --prop:/instrumentation/nav[1]/frequencies/standby-mhz=115.1001 --prop:/instrumentation/dme/frequencies/selected-mhz=115.8001 Torsten ------------------------------------------------------------------------- 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
