On 20 Mar 2010, at 22:24, David Megginson wrote: > It would take hours to sort out the code to see what's actually > happening. The new init functions make things even more confusing, by > including strange side effects (for example, setting the heading now > sets the azimuth to a VOR or airport, and may also set the selected > radial on a VOR). I used to help a lot with this stuff, but I don't > think I have the energy now.
There's another bug (in 2.0.0) to do with the GPS interaction with the nav[0] selected radial - I must say I've assumed all problems with --nav1 options misbehaving are ultimately caused by this bug, but it sounds as if you think there's worse things going on. It would help to explicitly define what the desired behaviour of the options is - and obviously, the nav-radio should work entirely in magnetic headings. As the person most recently hacking the navradio code, I think that's still more-or-less the case, but some bugs have presumably crept in along the way. (I tend to test around my home airport, EGPH, where the magnetic variation is not very noticeable compared to many other parts of the world) James ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
