Ticket #231 (assigned defect)

Opened 6 years ago

Last modified 5 years ago

Index out of bounds exception when ESS is not last or second to last turn point

Reported by: freitag Owned by: joerg
Priority: minor Milestone:
Component: FsComp Version:
Keywords: Cc:

Description

If there is more than one turnpoint (goal) after ESS, and a pilot reaches ESS, but not goal, FS produces an "Index out of bounds" Exception when processing that pilot's track.

Stein-Tore already has a fix for this, he asked me to file it as a ticket to keep the process going.

Change History

comment:1 Changed 5 years ago by ste

  • Status changed from new to assigned

comment:2 Changed 5 years ago by ste

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

Fixed, needs testing.

comment:3 Changed 5 years ago by freitag

Tested with the original competition, and with tasks that have even more turn points after ESS - works fine.

comment:4 Changed 5 years ago by ste

  • Milestone changed from 1.2.14 to 1.2.14.2

comment:5 Changed 5 years ago by oyvellef

  • Status changed from closed to reopened
  • Resolution fixed deleted

We've a problem with the results of the latest Placivel/Venezuela? competition run last december, and we're urged to solve it, civl and pwca are waiting for them !

We're using FS version 1.2.14.2 (the last one) and for us, the problem apparently solved by Stein-Tore in ticket #231 still remains for us.

In task 3 originally we have:

... ESS B2 1000

B11 2000

GOAL B2 400

That means the task included a turnpoint between the ESS and the GOAL, other that the ESS and GOAL turnpoints.

Some tracks give an out of range index error.

We've tested some variations of the task in order to understand the error:

0) the original task ... ESS B2 1000

B11 2000

GOAL B2 400

1) test 1 .... ESS B2 1000 GOAL B11 2000

2) test 2 .... ESS B2 1000 GOAL B2 400

We have run the 3 test cases and the results (we include only the case of 2 pilots but others are involved) are as follows:

Pilot # 30 in 0) has an index out of range error, but in test cases 1) and 2) he has no problem and the goal is achieved.

Pilot # 42 in 0) has an index out of range error, in test case 1) has no problem, but in test case 2) has an index out of range error.

In the ticket #231 someone reported this kind of error, and is congruent with the case of pilot # 30 (if the intermediate turnpoint is eliminated, no error is produced).

Nevertheless it is not the case with pilot # 42, for which the error is present (or not) depending on which turnpoint is eliminated.

The error is also affected changing the close time of the turnpoints.

I hope this will help to further understand and solve the issue.

Please feel free to contact us if you need more information.

Find here attached a .rar with with the error screen capture, the FS db file, all the .kml tracks, and the turnpoints file .wpt, in order you can mount the whole task and make the tests.

Thank you in advance

Best regards

Pablo Lischinsky

comment:6 Changed 5 years ago by joerg

  • Owner changed from ste to joerg
  • Status changed from reopened to new
  • Milestone changed from 1.2.14.2 to 1.3.0

comment:7 Changed 5 years ago by joerg

  • Status changed from new to assigned

comment:8 Changed 5 years ago by joerg

  • Milestone 1.3.0 deleted

Milestone 1.3.0 deleted

Note: See TracTickets for help on using tickets.