In addition, it will be great if XCSoar would use the same algorithm as OLC/SeeYou to determine release point so the distance will be more accurate.

I am not sure. Currently you get what you have achieved now and not what you could achieve theoretically and that is the info I actually prefer. Also the next WP is definitely not normally the finish of your OLC task. If you plan your task with the route planner (respecting the OLC scoring rules regarding the legs) you can always simply add the value of the "Fin Dist" infobox. If you desire to go straight home (ignoring the planned task) add the value of the "Home Dist" infobox.

I agree that if you plan your task with the route planner, than there is no need to calculate the total distance since you already know it in advance. In fact, there is no much need to the OLC infobox at all in this case. However how many pilots who only fly for OLC distance use the route planner? I believe 90% do not set any task since there is no need to set a task when you fly for OLC. At least no one who I fly with ever set a task for OLC flights. But many try to fly certain distance (300k, 500k, 1000k) or certain score (to jump up on the overall ranking for example) and as such, will find it VERY helpful to know when they can turn and fly back home. I know I do. When I flew with winpilot, which calculated the whole distance to the next waypoint (which will normally be home when you don't set a task) I kept looking on my olc distance until I achieved the distance I wanted. Having to add the distance to the finish is an unecessary extra workload, and in some cases such as when you already flew 6 legs, will yield the wrong result, since the correct optimization should be to your finish not to your current location + remaining distance.
The way it is now is inconsistant with winpilot and (I believe) also with SeeYou?.
I realize I may not be able to convince everybody, as such I suggest it to be either an additional infobox, or additional configuration to choose between achieved distance to total distance.

Any chance we can get this option in 6.3?

Changed to 6.3 as a last attempt to get it in. I really wish that OLC distance will be calculated correctly to your next waypoint rather than your current place. After all, you most likely not going to land below, so what value does it have currently? The main use of OLC distance it to know your results at any momemt assuming you will make it to your next waypoint, or your final waypoint/home (whatever you selected as Next waypoint). This way you can know if you already achieved your desired distance (or points)assuming you can make it home. The suggestion above to add the distance home is incorrect, since the distance is alreay optimized for 6 legs so adding the distance home will usually give higher distance than the final calculation. I just had an example in my last flight. I flew here and there and by the end of the day I calculated that if I fly a little further, I may squeeze a 500km out of it. But how far should I go? should I add my distance to home, or only part could have teold me that. The solution is simple, instead of calculating to current position, calculate to next waypoint. If you think that some people will prefer it otherwise from whatever reason, than make it a seperate infobox, or better yet, add a checkbox to the OLC section of the Task Rules configuration page to indicate how OLC distance should be calculated. I hope this can be included in 6.3 for those of us who fly for OLC distance.

I also make flights targeting specific OLC distance without a prior route plan.

So, like Ramy I also wish I had this feature to calculate my OLC distance to the destination more accurately than 6 legs to current position and having to mentally add the last straight distance to the destination.

If calculating an optimal 6 OLC distance to the next destination is too complicated at this stage, perhaps the next best thing in terms of accuracy is to calculate a 5 leg optimization to the current position and just add the straight line distance to the currently selected destination and show that in the infobox. This should be pretty simple and we could test it this coming season and see how well it works.

What do you think?

Thank you,

David

Glad to see I am not the only one :-)
To clarify, if it was only a question of mentally adding the distance to home I could leave with it (when I am no hypoxic...). However this will often give wrong result as in my example above. My last leg home did not add any OLC distance since the 6 leg optimization did not count the last leg.
From the same reason, even calculating 5 leg optimization to current position and add the distance back home will not be accurate as well. The error may not be big, but enough to make the difference between a 995km and 1005km flight...
I don't see why it should be any more complicated to extend the calculation of OLC distance to the next waypoint. I know at least Winpilot is doing it successfully.

Perhaps to clarify, many of us that fly in the Sierras launch as early as possible and stay up until close to sunset. Our goal is to maximize our OLC distance but we also have goals like 500km, 750km or 1000km. Speed to finish is not a goal in these flights. We pick the best route of the day as we go along.

So having an accurate OLC distance measure is very important for this type of flights.

Can we get more feedback from developers about this ticket? Thanks.

There was not enough time to implement it in XCSoar 6.3. It will be considered for the following release cycle.

Changing from Wishlist to 6.4 as I am hoping this will be implemented by then. It is not possible to decide when to make the last turn to achieve certain OLC distance, or to predict the OLC distance to home.
The following is an excerpt from LK8000 showing how they going to implement this (sorry for that, but it doesn't sound like I can convince otherwise):

​http://www.lk8000.it/new-20-features/22-olc-and-fai-calculator.html

Calculation in realtime for:

OLC classic
FAI triangle,
FAI 3 turnpoints
OLC sprint league
OLC Plus

In addition, also the same paths are recalculated assuming the pilot can make it back to the starting point, thus PREDICTING the final results.

All values updated in realtime, automatically. Very light CPU load, will allow also very slow CPU to use the new engine.

Prediction? What are you predicting?

You normally flight and read the distance achieved so far. Then you try to calculate manually "what if I can make it back home?" .

LK is doing constantly also this kind of calculation for you, automatically.

This is very important for FAI triangles, also. Because we are practically adding one more "leg" to your path. This last leg is predicted.

Please don't constantly change priorities/milestones of bugs. Thank you.

Since Max wrote that it will be considered for the following release, i changed it to 6.4 which is the following release. And since I opened this ticket I assumed I can change the priority and milestone. I would have appreciated much more if Instead of just downgrading the priority you would provide some feedback to this request, such as why you think it is not important enough to even be considered for next release. Your only comment so far suggested to add the distance home but this is incorrect as i explained above. If it was correct than my 480km flight last week would have been over 500km. The current OLC calculation missleaded me again. Your last comment was that you were not convinced, so I was trying to convince you. If you are still not convinced, perhaps another XCSoar developer will be willing to address it in 6.4, hence I would like to request to change it back to 6.4. It is an important request for those of us who fly for OLC distance instead of predefined task.
Anyway, thanks for all the great work you and other developers are putting into XCSoar. But please don't ask us for feedback then blow us off.

Changed subject to better describe the enhancement request.

From apf:

Currently you get what you have achieved now and not what you could achieve theoretically and that is the info I actually prefer.

I agree with that and prefer it the way it is. Sorry to disagree, Ramy.

Last new feature for 6.4.

4b6a4996b982550a5dc3bd4ede649a6a102aecb1

Ramy, congrats to the 1000km flight!

Thanks Max! This will help making 1000km flights instead of 999 :)
And thanks for removing the captcha!

Ramy