Develop

Ticket #2183 (closed defect: fixed)

Opened 11 months ago

Last modified 10 months ago

AAT Calculations Missing

Reported by: luke Owned by: max
Priority: high Milestone: XCSoar 6.3
Component: Other Version: 6.3
Keywords: Cc:

Description (last modified by onkelhotte) (diff)

When creating the task the Turn Areas are just big cylinders but all the calculations are done to the center of the Turn Area, not the optimized point. The Target button is missing from the calculator. You can change this by making the task to racing, exiting out of task planner, going back into task planner, setting the task to AAT then exiting the task planner again. I have confirmed this with 2 other XCSoar users. After I roll back to 6.3.4 the issue disappears.

to reproduce
go to task manager > new task
rules = aat
min time= 3h
insert some points and adjust cylinder size

issues: no optimizations available for the cylinder, can not move target, target button missing, only distance to the center calculated, no min/max

exit out of task planer and select "fly" all issues above are still present

go back to task planner change type to racing, exit flight planner select "fly"

go back to task planner change type back to AAT, all optimizations and target options available, exit out of task planner, select fly all is well until you need to add a new Turn Area (task modified in the air before gate opens etc etc)

adding a new Turn Area into the task creates a new big cylinder without any optimizations, all calculations are done to the center for the case of this Turn Area.

Change History

comment:1 Changed 11 months ago by max

I cannot reproduce this. Everything works as expected.

comment:2 Changed 11 months ago by xtophe

Luke,
Are you trying in sim or fly mode ? If in fly mode, do you have a valid GPS position ?

comment:3 Changed 11 months ago by roman

It seems that if Task Defaults>Turnpoint Types Task is set to "AAT" and a new task is created the above problem will occur.
A telltale sign (at least in sim mode) is a missing message "In sector, arm advance when ready" after take-off.
If the default turnpoint type is set to "Racing" and the "ATT" is explicitly configured while a new task is being created, everything works fine.

comment:4 Changed 11 months ago by bernie01

I can reproduce this in 6.3.8 Android.
It occurs in fly mode when there is no GPS fix. Once there is a GPS fix, the target icon appears. In Sim mode it is OK.

comment:5 Changed 11 months ago by luke

Sorry guys, long days at the field, in the middle of the contest. This happened in fly mode with valid GPS signal from 3 sources (CAI302, FLARM and Built In Dell Streak 5). I can provide my PRF and wp file if need be.

Luke

comment:6 follow-up: ↓ 7 Changed 11 months ago by max

bernie01: this quirk will be fixed in 6.3.9.

comment:7 in reply to: ↑ 6 Changed 10 months ago by onkelhotte

  • Description modified (diff)

just playing with 64b1- on my ipaq 38xx

something strange - indeed.

creating the task, "close" and "fly" -> "nav" -> "nav" -> "target" the optimization check box appears for app. 1/2sec and disappears??

playing with 6.3.10:
obscure!

I played today with an old saved task from Dosi-Competition in Oerlinghausen and everything worked well (6.3.10).

After starting (not installing), 6.4.b1, the optimization checkebox disapeared as described above.

I wonder:
from then on this happens in 6.4.b1 AND 6.3.10... ???

testing testing:

Found it:


You can reproduce that with the things written by roman:

If the default turnpoint type is set to "Racing" and the "ATT" is explicitly configured while a new task is being created, everything works fine.

yepp.
that's it.

So it has something to do with the default settings to "AAT" in the system configuration.

Last edited 10 months ago by onkelhotte (previous) (diff)

comment:8 Changed 10 months ago by max

  • Owner set to max
  • Status changed from new to accepted

comment:9 Changed 10 months ago by max

  • Status changed from accepted to closed
  • Resolution set to fixed

b5657de30d37a593f5059001aae25328d91c311a

comment:10 Changed 10 months ago by max

correction: 03809239c5a1697b5e64ff6bf493092240aa2a4b

Note: See TracTickets for help on using tickets.