Hi,

 

just a (may be) silly question: Did you actually have a flight plan loaded in your last test flights? If you did, all the metars (in 80nm range IIRC in ASE) should match. If this was not the case, then yep this is a bug.

 

I am sure you did load a FP in your first post, but I really think in that case the issue is when the surface visibility is "enforced" compared to the upper visibility. In this case, vis graduation is most possibly the problem (that's why I initially suggested a low graduation ceiling and/or disabling vis graduation). Disabling vis graduation has its drawbacks, but should be more reliable in these circumstances.

 

Kostas Terzides,

Active sky developer

Yes I do fill a simple entry of DEPARTURE and DESTINATION each time (KFRG KJFK).

Destination weather is certainly not locking (stable) during that short flight.

KFRG is in fog, and few miles north it clears up.

 

Kostas I don't think it has to do with Vis. grad.

After all I don't find it apropriate to start disabling every single feature of a software just to get the visibility right.

We have paid for ASE to get its advanced features, not to disable them all !

 

Whatever I did (before the stations mod.) the KJFK fog would not come up until 2DME / on ILS22L and it would also always disappear at 0.6 DME while rolling on the runway.

In all other areas near KJFK visibility was clearing up again.

It is clear something else if forcing it to come and go so close to JFK and what I found was that mainly the 10SM vis of LGA was the imposing weather station data bit.

Even though destination was set KLGA is affecting it by being 10 miles abeam JFK.

 

You can also tell from the colors of the above screenshots that other visibilities are affecting JFK apart from its own yellow visibility cloud.

 

I even tried it in slew mode moving slowly back and forth.

 

All of the above are in tests with the off line weather report mentioned in previous post.

Hi,

 

observing this bug also.

 

Win7 64 bit, FS2004, ASE Sp4 here.

 

Mainly flying with offline weather and i'm able to observe that behaviour described in this topic frequently. It's a long time ago i gave up requesting for support.... Even there are more bugs, e.g.: never showing correct date and time; changing the weather file via ASE user interface doesn't work - if i'm lucky it perhabs works for the first time but after more times just nothing happens.

 

Thank you Kyprianos Biris for telling these words "After all I don't find it apropriate to start disabling every single feature of a software just to get the visibility right. We have paid for ASE to get its advanced features, not to disable them all !"

 

I'm totally with you!

I think we're talking about 2 different problems here.

 

@Rob, do you use DWC?

@Kyp, it's Damian's call, what is included in a SP (given the time restrictions and our need to move forward). What you can do now is to disable vis graduation. This way surface visibilty will "suddenly" come up when you are at least 3000 ft agl (at least it should).

I do use DWC.

 

I will try disabling graduated visibilty.

 

Should the Fog Layer option be enabled or disabled?

ASE - do I need to create a ticket for this previously reported issue?

i guess I'll create a ticket :-)

Ticket submitted. Referenced this thread in the ticket. Will keep yous posted.

 

#FKN-725-51349