I would also like to see bugs persistant (like SeeYouMobile). I also use
bugs to degrade the polar since the polar always seems to be optimistic.
Better yet, I would like to see a polar degradation control (in%) which is
persistant and conneced to a particular polar. One would trim this in over
a few flights. I hate seeing my reserve disipating
Peter
On Sat, Nov 5, 2011 at 7:56 PM, Olaf Hartmann <
olaf.hartm...@s1998.tu-chemnitz.de> wrote:
>
>
>
>
> Ramy Yanetz <ryan...@yahoo.com> schrieb:
> >1 - I believe many (most?) of us use XCsoar
> >mostly for 'casual' XC or OLC, and less for contest/record/badges,
> >which means in most flights no task is set. It is not clear to me what
> >is the recomended strategy to configure
> >XCSoar to this most common type of flying. The most important
> >information for the casual XC pilot is distance, direction and arrival
> >altitude at various landout places along the course, using conservative
> >
> >glide angle (typically half to 2/3 of published polar).
>
> One alternative might be to show required l/d values for each outlanding
> field instead of arrival height. There is a ticket for that. I think i like
> the idea and will give it a try.
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Xcsoar-user mailing list
> Xcsoar-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xcsoar-user
>
--
Peter Cutting
+46 703 580073
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Xcsoar-user mailing list
Xcsoar-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcsoar-user
