On 2011/11/22 20:13, Ramy Yanetz <ryan...@yahoo.com> wrote: > 2 -MC is not just for expected thermal. If your final glide is against the > wind as in these examples, you need to set your MC > 0 in your flight > computer (eg 302) to get the best glide speed, even if you don't expect to > circle again. This is in fact why I noticed this problem, since I increased > my MC to 0.5 in my 302 (which automatically updates XCSoar) to compensate > for the 12 knots headwind, and as a result my arrival altitude > instantaneously dropped by over 5000 feet. This can never be correct in any > logical way. if it was correct I would have landed out.
So your legacy glide computer is incapable of considering the headwind properly in a glide calculation. And you found a way to fool it by setting some random MacCready value. Again, this is doing it wrong: you see that the 302 result is not correct, and then you edit the MacCready value until the result meets your expectations. Please tell me your formula that turns "12 knots headwind" into "MacCready 0.5 m/s". And tell me how this is relevant to XCSoar. 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
