I simply think that this "do not consider wind drift" solution will help provide anything reasonable in many of the other calculations. Especially for low performance gliders like a Ka8 wind drift can be the absolute dominating factor even in moderate wind. By not considering it everything falls apart. Tasks may be shown as achievable when they are not, all the time calculations will be completely off (with the result that you might not make it back in time for sunset / end of lift) and what is even worse, if your outbound track is with a tailwind you will not even beware of the problems until you turn back.
Instead of looking for a solution for papering over the effects of a deliberately provided wrong "MC" setting we should try to educate pilots not to use a MC setting as some kind of tuning knob to influence the calculations towards something the pilot wants to achieve. Take and use the MC setting simply for what it is, the expected lift of the next thermals and everything will just work and correctly tell you if something gets borderline/impossible. If you want to build reserves nothing prevents you to fly slower than the "Speed to Fly" which results from that MC setting. Sensible MC settings is all that is needed. For most gliders the range from 0.0 to 1.0 will not cause major different glide rates due to "Speed to fly" anyway however the drift will vary significantly in that range. Also in the presence of a headwind a slightly increased "Speed to Fly" above best glide-rate speed will even increase your glide range. And last but not least: This xcsoar behavior is not new. It is present since 6.0 and until now nobody seems to have had any problems with it. And it only effects the final glide bar and some of the infoboxes. The arrival heights in the map are completely unaffected since we only did show positive arrival heights anyway where drift does not need to be considered. This discussion has made me aware that "old habits" which were necessary and helped somewhat for the old generation simple glide computers are difficult to change. Instead of introducing yet another set of config options which will make understanding what really goes on in an already complex environment even more difficult try xcsoars method. Personally I think that xcoars calculations are far more useful since they are more realistic and will be appreciated by all who give them a chance. I have been very pleasantly surprised during my unfortunately few longer flights in windy conditions by the exact predictions of xcsoar (with MC set to AUTO). ------------------------------------------------------------------------------ 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
