Opened 8 years ago
Closed 8 years ago
#261 closed defect (wontfix)
Pilot A reaches turnpoint, pilot B not, but distance of A < distance of B
Reported by: | Brian Harris | Owned by: | Joerg Ewald |
---|---|---|---|
Priority: | major | Milestone: | 2013 R2 |
Component: | FsComp | Version: | 2013 |
Keywords: | Cc: |
Description
In T1 pilot 22 scores less distance than pilot 49 , pilot 22 reached TP4 (although he is off the optimised line he has points inside the cylinder , whilst pilot 49 does not reach TP4. This does not seem correct , although I am not quite sure how the arc back to the track is drawn.
Attachments (2)
Change History (3)
Changed 8 years ago by
comment:1 Changed 8 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
I'm afraid this is a freak case we can't do much about. FS calculates the distance a pilot reaches as follows: total task distance - distance left to fly.
In the case here (see attached screen shot), pilot 49 (black) crossed the turnpoint cylinder to the north, the closest he got to it was about 300m (red marker on track). So his distance left to fly is these 300m, plus the last leg to goal to the north.
Pilot 22 (red) crossed into the turnpoint cylinder on its south side, the side that is the furthest from goal. So at his optimal point (red dot) he still had to fly all the way through the cylinder (about 600m) before starting on the final leg to goal. So clearly his distance left to fly is greater than pilot 49's.
Reaching a turnpoint or not does not really have any significance when measuring distance - it's all about how close to goal you got. This was different in the old days, when we were still aiming for the cylinders' centers, and got awarded 2x the cylinder radius in extra distance as soon as we hit the cylinder's edge. But I think this is much more accurate and fair.
So I put this on "won't fix".