On 2011/07/19 22:12, Tibor Arpas wrote:
> On the other hand it could make automated testing of a set of igc files
> easy(?) so that even alpha users would be faced with this kind of crash
> really unlikely.
We already have many special-purpose programs to test many aspects of
the XCSoar code, inc
This would make the crash at the same spot more likely (making the task
resume unusable).
On the other hand it could make automated testing of a set of igc files
easy(?) so that even alpha users would be faced with this kind of crash
really unlikely.
And maybe could bring us closer to a function
On Tue, 2011-07-19 at 20:17 +0200, Max Kellermann wrote:
> On 2011/07/18 23:53, Tibor Arpas wrote:
> > Please let the developers know if you need this functionality. Thanks a lot.
>
> We could store just the trace, or recover from the partial IGC file to
> fill all the task engine internal variab
On 2011/07/18 23:53, Tibor Arpas wrote:
> Please let the developers know if you need this functionality. Thanks a lot.
We could store just the trace, or recover from the partial IGC file to
fill all the task engine internal variables (internal replay).
That'll take some CPU power, but we could sk
Thanks everybody for feedback.
Tobias, but when XCSoar or your device crashes then you're blind about the
arrival time, right? Or maybe you have some backup..I would like to avoid
buying expensive instrument just to have backup for the AAT calculations.
I've used quite unstable HW/SW configuratio
On Tue, 2011-07-19 at 09:15 -0400, Luke Szczepaniak wrote:
> Hi everyone,
>
> Perhaps a way to manually set the start time after the begging of the
> task would allow XCSoar to continue with the appropriate calculations
> after a crash has occurred. Better yet, every time XCS detects a
> start it
On 7/19/2011 9:15 AM, Luke Szczepaniak wrote:
> A simple button "load last start" could be placed somewhere in the
> Nav/Task menu.
>
Excellent idea. Start logic is always difficult. There are a lot of
ways this can get goofed up (operator error chief among them). I like
the idea of 1) bei
Hi everyone,
Perhaps a way to manually set the start time after the begging of the task
would allow XCSoar to continue with the appropriate calculations after a
crash has occurred. Better yet, every time XCS detects a start it writes a
temp file containing the start time height and speed as shown
On 18 July 2011 22:53, Tibor Arpas wrote:
> Hi guys,
>
> I would like to ask those of you that fly competitions if you are happy
> flying AAT tasks with XCSoar? During the two competitions I used XCSoar I
> came too soon too many times. Once I made a user error and a couple of time
> XCSoar crash
Hui, Tibor
I've flown a couple of AAT in Klix 2011 and won 3rd place on DD. My
friend flow FF and won 2nd place. We flew with XC 6.09.
I had no bugs or crashes at all, but in comparison to WinPilot (which
was used parallel on flight), XC is calculating a little bit to
pessimistic,
that indeed
Hi Tibor,
I'm flying competitions regularly here in Germany and I love the AAT
auto-optimization of XCSoar. With my PDA (Asus A636 with WM5) I rarely
ever have crashes. Since I usually fly with an unstable testing version
there are some, but most are fixed a few days later. I agree though that
Hi guys,
I would like to ask those of you that fly competitions if you are happy
flying AAT tasks with XCSoar? During the two competitions I used XCSoar I
came too soon too many times. Once I made a user error and a couple of time
XCSoar crashed during the flight. I don't think that the crash itse
12 matches
Mail list logo
