It's actually even more confusing than that: the initial value seems to depend on whether the --vor option is selected, what the heading is, etc.
All the best, David On Sat, Mar 20, 2010 at 6:09 PM, David Megginson <david.meggin...@gmail.com> wrote: > There's a bug in the /instrumentation/nav/radials/selected-deg > property: the code mistakenly assumes that the selected radial is in > true degrees, but isn't a bearing -- it's just a number. You could > design a VOR where radial 180 was north of the VOR, if you wanted to > (though usually it's close to a bearing in *magnetic* degrees). The > bug affects the --nav1 and --nav2 option in particular, since > > --nav1=340:114.6 > > will no longer start FlightGear with the Nav1 indicator dialed to the > 340 radial, unless the local magnetic variation happens to be 0. At > CYRO, for example, the actual radial ends up being closer to 326, > which is counterintuitive. Nav radios and indicators know nothing > about magnetic variation. > > We used to have this right in FlightGear, but it's gotten messed up > over the last 3-4 years. I'd like to fix it, but I'm worried about > how many places we've hardcoded this assumption. How hard will it be > to correct this? How many of you have designed radios, autopilots, > etc. counting on this bug? > > > Thanks, > > > David > ------------------------------------------------------------------------------ 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
