Hi Jax, I guess the problem is that we don't have any active australian developers at the moment and nobody else is using such a rule. As for the arming: there was a bug in the task handling that was fixed lately but the arming behaviour shouldn't have changed. Can you find out when it changed (from version x to version y) and what exactly changed? Our plan is to make it configurable (arm start = yes/no) for the future but I can't promise that XCSoar 6.4 will already include it since I'm not really the guy for the task stuff.
Turbo 2012/6/27 Jacques Graells <jacques....@gmail.com>: > Well I guess not many people use XCSoar for multi starts AAT’s, we’ll hope > and patiently wait till enough people have a need for it. > > > > Cheers > > > > Jax > > > > > > > > From: Bernie Baer [mailto:bb...@internode.on.net] > Sent: Tuesday, 26 June 2012 10:39 AM > To: xcsoar-user@lists.sourceforge.net > Subject: Re: [Xcsoar-user] AAT tasks behaviour > > > > > > Jacques raises some very important points for those of us flying AAT's, and > particularly using multiple start points. > It seems that removing the 'Arm Start' option has caused most of these > issues, and reinstating it would solve most of them. > > Re point 1: 'Arm Start' needs to be reinstated > Re point 2: As Jax says, this is very undesirable behaviour. > Re point 3: Stretching my memory, but I think this was previously available? > If so, reinstating it would be good, but I could live without it also. > Re point 4: Again , undesirable. 'Arm Start' reinstated would prevent that I > think. > > Re point 5: I don't quite understand the issues Jax mentions here. However I > have only flown AAT's last year using V6.2.3 and the optimisation worked > quite well. > I would like to play and test this in a current version, however as already > reported in a Bug Report, the 'Target' button is not present when there is > no GPS signal (like in my study!). > This needs to be fixed. > > Re point 6: Again, with V6.2.3, the optimisation worked quite well. I didn't > come home 15 minutes early, usually just over time as desired. > > Re point 7: Obviously a bug; the chosen default start point diameter (or > any parameter) should apply to all SP's including alternates. > > Regards, Bernie. > > > Quote: 'Jax' > > Since V6 there has been many changes to the AAT tasks in XCSoar and it is at > a point now where it is a quite difficult to use it for AAT and particularly > multi startpoints AAT. > I'd like to share some behaviours of the current version 6.3.8 so perhaps > people can express their wishes of how it should work and the developers can > look into it. > I understand that multi starts AAT are not used everywhere but here in > Australia, unless it is a GP, in any given comp you will get an AAT day and > most of the time it is with multiple starts. > > 1) We no longer can Arm the start, the task is armed from the beginning > of the flight. This particularly annoying when waiting for the gate to open > and fly in and out of the start sector, the task keeps starting and > re-starting. > > 2) If we select a SP via Next Startpoint button and enter another SP > sector, then the target becomes the SP we just entered rather than the one > we selected. > > Here is a case where it is a real pain > We are in a comp and we are assigned 3 different SP SP1, SP2 and SP3. > Based on the wind and location we decide to start on SP1. > We select SP1 using "Next Starpoint" button. > While waiting for the start gate to be open then a cloud pops on SP2 and we > decide to go there. > When entering the SP2 sector the target start changes to SP2 which we do not > want. > When leaving SP2 to go to SP1 the task starts and the target become TP1. > We then need to select previous TP in XCSoar and cycle trough the SP till we > have SP1 as target again. > > 3) There is no notification where we enter the starting sector > Obviously this makes us having to look at XCSoar more than desirable at a > busy time when flying in close company of many other gliders. > > 4) If we fly through another SP after starting the task the task > re-starts. Depending on our intention we should be able to prevent that > behaviour. > > 5) The optimisation is not very flexible, either it picks the point for > you which is generally not appropriate for an AAT or you pick the point and > you have to time your turn ie what is XCSoar supposed to do for you. What > would be nice is if we can give directions to XCSoar and it make picks the > point for us, as an example give a heading and XCSoar adjusts how far to go > in that heading. > > 6) In my experience the calculations for time are always extremely > pessimistic, if I make my turn for and arrival at +5 minutes, I will > invariably be early. > > 7) When changing the diameter of the start point after alternates have > been defined, the alternates do not change and the only way to change them > is to delete them and re-create. > > It would be good if we can have feedback from other pilots about how they > think XCSoar should behave for AAT multi starts > > Cheers > Jax > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Xcsoar-user mailing list > Xcsoar-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xcsoar-user > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Xcsoar-user mailing list Xcsoar-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcsoar-user