XCSoar / LK8000

On Monday, March 11, 2013 2:49:06 PM UTC-4, Luke Szczepaniak wrote:

From my experience last year, V6.4 was very stable, all rules and

optimizations worked as necessary.

That's interesting. The task optimizer -- which worked marvelously well for me in about July of 2011 -- was busted as of late Summer 2011 and I d/l'ed whatever release was current late Summer 2012 (i.e. a year later) just to see if that had been fixed... and found it hadn't. In my case, I always had to enter silly high Mc settings to get reasonable expected XC speeds. I got blown off on that... I guess it wasn't judged to be "serious" :-). The suggestion to add a dirt simple manual override for projected XC speed was likewise rejected.

I agree that figuring out a way to minimize the poking and prodding is a good thing. I liked the visual presentation of the Streak.

Evan Ludeman / T8

I suppose you are talking about the AAT task optimizer? I've flown two competitions with it last year, and it worked as well as always before... It would be great though if you could point us to the first version that behaved badly for you, because otherwise we can only do wild guesses too.

For me the connectivity of Android based systems is important. I
like to connect with FLARM, variometer and logger. (I am also
dreaming of GPS-NAV communication with XCSoar).
After using Android device going back to Windows CE is not easy.
Mobile communication sends my position into web server, and
maybe I can track my friends online while flying.
User interface is IMHO the problem of all these touch devices.
Simple buttons or rotary switch would be better in turbulence.

For me the most important feature is the moving map and airspace
limits and FLARM traffic view. Then maybe the final glide
calculation. I fly with voice variometer.

On Monday, March 11, 2013 4:10:31 PM UTC-4, Tobias Bieniek wrote:
I suppose you are talking about the AAT task optimizer? I've flown two competitions with it last year, and it worked as well as always before... It would be great though if you could point us to the first version that behaved badly for you, because otherwise we can only do wild guesses too.

The task calculator, yes.

There was a problem early on in 6.3 that did get sorted out. That problem caused my XC speed predicted vs Mc setting to run very high. I wrote a ticket, it got worked on, many thanks.

Later on, I noticed the inverse: entering for instance Mc 3.0 (knots) would yield an anomalously low predicted XC speed, low 40 mph range. This would have been with what ever version of XCS was current in April/May 2012, 6.3..something. I pulled out my Dell Streak to see if I could reproduce the problem quickly and I cannot, so I withdraw the shot about not being fixed a year later. The version I have loaded is 6.4.5. Mc 3.0 yields 51 mph which is about right if cruising is done in still air for dry ASW-20A, which is the polar I have loaded. Of course we always try to cruise in better than still air, so it's a good thing to be able to tell the nav device that "yes, the next 40 miles are going to be *really* good" due to ridge, cloud street, convergence or what have you. Having to set the Mc value, observe the speed calculated, deciding if it's reasonable, adjusting again maybe and *then* looking at the turn areas to see how far I need to go is a gigantic pain in the ass and an unreasonable waste of time in the cockpit. It's much easier for me to simply estimate speed (based on experience and what I see ahead) and work from this. I find that I can estimate speed quite well for days that go well. On the days that don't go well, I don't care about speed, I just care about getting around and the calculator is of no real import. Anyhow, my $0.02. Sorry I can't shed any illumination on whatever the issue was, perhaps it really is all fixed now.

T8

Having just got into gliding and looking to what software will run, what it offers etc i came across lk8000 and xcsoar, both very good. My first reaction is that two groups of very capable developers have gone separate ways( it doesn't matter why) to develop for the good of glider pilots. Now everyone in life wants different, the world over! Both free, people can download both and sample which they prefer. I personally found lk8000 easier to set up. But haven't used either enough to pick one. As a fixed wing power jock I use skydemon on a mini iPad. I think this suits MY purpose over the others.
With lk8000 and xcsoar you could use both on a tablet pc.
Lets stop the public debate from the developers claiming who has the best! I think it very unprofessional and doesn't affect my judgement as to which I prefer, once I've used both I have no doubt that I will pick one ov er the other.
To the develops, just go out to have in your opinion the best product, don't worry about the competition. The end user will decide on the best. They probably isn't a best as everyone has different ideas on what they require.
Lets all be thankfully that we have a free choice and that people are able to develop software of this complexity and give it away.
From me thanks to both the lk8000 and xcsoar team. Keep up the good work.

I use a car navigation system, (a Mio Moov, was cheap, like $100 if I recall) and it runs LK8000 great. The display can be a little hard to read in the sun but the new airspace views of LK8000 (both top and side) have been fantastic... our gliderport is underneath the edge of a class B so it's been really helpful to keep track of where I am regarding the airspace above.

Also, clicking through the screens is fast and easy.. the earlier versions of XCSoar (I can't speak for the newest) required clicking tiny little buttons and scroll bars, and thats something that just isn't going to work for me in the cockpit. LK8000 is designed around quick and easy navigation between screens with minimal distraction.. in fact you can identify screens by the sound they make as you switch without looking.

Try both is my advice... read the manuals for both... and watch youtube for examples of how things are done, then test fly them in sim mode or on a simulator.