See You : "Task Not Finished"

On Nov 11, 7:30*am, Big Wings wrote:
I'm wondering if SeeYou is confused by the fact that the flight wraps
around midnight (UTC) and apparently starts after it has ended.

When I run animation against the relevant IGC file its starts at the
launch time but when it reached midnight UTC (part way along the second
leg) it thinks the flight has ended and jumps back to the launch.

Looks like this could be a SeeYou bug - even if it's not the root cause
of the original landout problem.

I believe this is a known problem and I expect Naviter will be fixing
it. However if you set the correct UTC Offset in ToolsOptionsGeneral
this won't happen.

Darryl

On Nov 11, 7:41*am, Darryl Ramm wrote:
On Nov 11, 7:30*am, Big Wings wrote:

I'm wondering if SeeYou is confused by the fact that the flight wraps
around midnight (UTC) and apparently starts after it has ended.

When I run animation against the relevant IGC file its starts at the
launch time but when it reached midnight UTC (part way along the second
leg) it thinks the flight has ended and jumps back to the launch.

Looks like this could be a SeeYou bug - even if it's not the root cause
of the original landout problem.

I believe this is a known problem and I expect Naviter will be fixing
it. However if you set the correct UTC Offset in ToolsOptionsGeneral
this won't happen.

Darryl

NOT UTC, NOT 302A!
Problem was fixed by increasing the Observation zone radius in See
You, under 'Tools' / 'Options' / 'Observation zone'
Many thanks to 5Z (Tom) and everyone else who looked into this!

On Nov 11, 8:31*am, Uncle Fuzzy wrote:
On Nov 11, 7:41*am, Darryl Ramm wrote:



On Nov 11, 7:30*am, Big Wings wrote:

I'm wondering if SeeYou is confused by the fact that the flight wraps
around midnight (UTC) and apparently starts after it has ended.

When I run animation against the relevant IGC file its starts at the
launch time but when it reached midnight UTC (part way along the second
leg) it thinks the flight has ended and jumps back to the launch.

Looks like this could be a SeeYou bug - even if it's not the root cause
of the original landout problem.

I believe this is a known problem and I expect Naviter will be fixing
it. However if you set the correct UTC Offset in ToolsOptionsGeneral
this won't happen.

Darryl

NOT UTC, NOT 302A!
Problem was fixed by increasing the Observation zone radius in See
You, *under 'Tools' / 'Options' / 'Observation zone'
Many thanks to 5Z (Tom) and everyone else who looked into this!

I should have been clear, Tom clearly had nailed it, but the UTC
offset will catch people if a flight wraps as Big Wings reported. It
may not be an issue, or you may have the offset set correctly in
SeeYou on your PC. This comes up when people view a flight trace from
a different timezones, and may need to reset their UTC offset to work
around this.

Darryl

On Nov 10, 7:13*pm, 5Z wrote:
Consider a 50+ km diameter thunderstorm sitting on top of the
turnpoint. *If using a camera to document the flight, you might just
be SOL due to not being abole to see any landmarks at or near the
turnpoint.

But wasn't it ok to verify being in the sector by photographing a
recognizable feature in the sector rather than the TP itself. I know
that was not valid for US contest TP but it was ok for badges and
records wasn't it? It's been a long time since I used cameras.

Andy