Author |
Topic |
Coolwind
Moderator
Italy
8957 Posts |
Posted - 13/01/2017 : 20:36:57
|
How can you validate a start? By passing the start point of course. When you do that, internal variables are updated with coordinate, altitude, and time automatically. I dont understand what is the problem, what am I missing? |
|
|
stoickov
Pulcino
60 Posts |
Posted - 17/01/2017 : 04:08:22
|
In my previous post I've given a real life example of how the issue may cause problem during a task. Yes, it involves human error, nevertheless it leaves pilot with no option to correct it. |
|
|
Coolwind
Moderator
Italy
8957 Posts |
Posted - 18/01/2017 : 02:54:00
|
You started this thread with a totally different issue, not knowing you need to start the task to get task values. Then you gave this example: "Task start is 11:45 You set it on your devices, but you mistakenly set time gate at 12:00 at LK. You start the race at 11:46, and you realize the time gate was set wrong at LK, so you switch to next waypoint, becaus"
This example is NONSENSE. Why? Because not only the pilot does not set up correctly the task, but after the takeoff for many minutes he does not look at the screen noticing that the task is due starting later. He does not look at LK for starting line (otherwise he would notice the wrong time gate). In real life, such a pilot realise there is a problem and has 3 choices. a. While waiting for gate open, reprogram LK time gates correctly. b. Land, correct task and takeoff again. c. Fly the task without statistics, looking at LK only for turnpoint selection, manually made.
It is not true that we leave the pilot with no options. He has options. What we cannot do, is to guess the altitude he is starting . We dont know it because we dont pick it up when he crosses the start line, simply because we dont look at the start line at that moment.
I am closing this thread.
|
|
|
Topic |
|
|
|