On 2011/11/22 21:34, Ramy Yanetz <ryan...@yahoo.com> wrote: > And since 302 gives my audio STF command, there is no other way I can easily > make it to tell me to fly a little faster than tweaking the MC, and since > this in turns update the MC in XCSoar, hence we have this discussion...
So it boils down to: you want to have different MacCready settings in the CAI302 and XCSoar? I worked hard to make linking them possible, and it's pretty easy to disconnect them for those who don't want it. We have a ticket for that already, IIRC. > Max, we both use the same setup of 302/xcsoar, so I am curious how you > address this scenario of a marginal final glide at the end of the day into a > buoyant 20 knots headwind without causing XCSoar to assume that you plan to > climb and recalculate your arrival altitude. The only way to do it will be > perhaps to add bug factor but this is not what it was designed for and takes > more effort. MC is more intuitive. MacCready is only intuitive because you've been learning all your life to do it that way, because legacy computers (and of course the good old MacCready ring) can't do better. It was a kludge based on limitations of the tools we had. It's not an issue with a modern glide computer. XCSoar will consider the wind in all calculations, and one doesn't need to increase the MacCready/Bugs setting to account for head wind. On your question: I use AutoMC. Max ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Xcsoar-user mailing list Xcsoar-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcsoar-user
