I did some more investigation in simulation mode and noticed the following:

• if no task is turned on (just a simple goto), the airspace warnings are working correctly, no probs
• if I turn on a task, the incorrect warnings are happening. In my example, my next turnpoint was in north. Frankfurt tight airspaces were in north also. I flew to south and the the warning is happening. But I fly south, still v6 warns about airspaces in north.

If you need I can film or prepare some more clear example.
Tomek

Screenshot showing incorect warnings while on task

Here is an another example on "strange" airspace warnings.
On the attached picture I fly south and have GOTO to waypoin to the north. After being above a certain hight, v6 will warn me on airspaces to the north.
From my perspective incorrectly. This happens eventhou if I am like 40km to the south.

Airspace Warnings incorrect 2

Another example of incorrect airspace warning

Not a bug, it's a feature. This is desired behaviour now, that your track through the task should give you plenty of advance warning that your track will intersect airspace.

John,
but this is not flyable, really. There must a some impact threshold at least. We have here in Germany A LOT of airspaces, in many cases tracks in their straight line will cross many of them. Getting warnings for airspace maybe more than 100km away does not help. Why the warning system does not use "warning time" impact time from system setup -> 2 Airspaces.
This must be at least configurable, otherwise I must disable warning system at all and this is not really helping.
Plse reconsider. Look at my example "Airspace Warnings incorrect 3.png"...
Tomek

I second that... it should at least be configurable...
the best solution however would be to calculate the shortest way around the problematic airspace or something like that, but I guess that depends on the weather anyway...

I tried flying a declared task on saturday and I had over 20 airspace warnings miles away... This is really annoying and it needs a lot of attention during flight. Here is my urgent request to either remove it, improve it or at least make it optional.

Yesterday I had a long flight with v6 again.
I just turned off airspace warnings at all. This is however not good at all, as you may miss something on the way, secondly the Airspace areas on the map will not "fill in" if warnings are turned off. This is dangerous.

Maybe a constructive proposal to set a certain threshold on the warning, so everybody can set it up as the like. I would keep for something between 30-60sec, others can have also 1000sec. Other approach would be distance or combination of both. "Filling-in" does not need threshold at all - is it good to see conflicting airspaces all the time.

John, plse in Germany with hindreads of airspaces around the current solution does not hold.
I would appreciate your help on that.

Tomek

perhaps we should simply warn the user if their planned task goes through airspace and offer them the choice of continuing (and then warning them when they are actually close), or viewing the conflicting airspaces?

I flew yesterday around eastern Pennsylvania, and received about a dozen warnings that I was near the Pittsburgh airspace, a large Class B airspace with several areas about 494km away. My task route was never closer than about 360km to the airspace.

I also received on false warning that I was _violating_ the Allentown Class C Airspace when I was about 5 miles outside it (correctly visible on the screen and confirmed by See You after the flight). No proximity warning preceded the violation message.

8/3/2010 build from Max's repository

UPDATE, build 7.08.2010
Airspaces warnings do not come up for airspaces very far away - GOOD.
The problem now is that warnings comes only when one is already inside - so too late.
We need "NEAR" option working, that considers warning time (default 30sec)

Tomek

Partially fixed by ed38e51398dc32710a6149f2da5013a7077bee22 (warning too late)

Fixed in 0d26e65fb3bf335f4c4b1d8526839705d4b17969