Hi,During my last 4 or 5 flights the surface winds at departure airports are allways 225/0 in ASA.My last flights departed all in France.Tonight leaving at LFST (Strasbourg) the winds again showing 225/0:Fireing up AS6.5 about a minute later, showed the correct surface winds:I noticed also other pilots reported this issue.In running FS9 and connected to FS via WideFSThese are my wind settings:Please advice,EgbertUhhrrrrr...Is this a user error :( I see that the max surface winds are set to 0kts ?!? Is that causing the issue?On the other hand, the METAR is totally different from the one in AS6.5...

Hi,My LFST is OK, and yes it is because maximum surface winds are set to zero.And also, in ASA it was Advanced Interpolated. And in ASv6.5 the data was an hour old.Thanks,

And also, in ASA it was Advanced Interpolated. And in ASv6.5 the data was an hour old.

Hi Jim,So if I'm correct, AS6 and ASA use different WX-servers?AS6 was started up a minute after AS6 (closing ASA first)Or does ASA interpolates if the METAR is too old, i.e 1+hr?I don't know how the surface winds were set to 0, but appearantly I must have changed it.I'll correct it and try again.Egbert

Hi,I tested this morning again with the same result, after having set the max surafce winds to 50kts in ASA.This is AS65, Winds 020/10 :In ASA again 225/0, 4 minutes later :Unless I'm doing something wrong, there is either an issue with the WX server or ASA.Please advice,EgbertEDIT: This is the METAR in the ..\Application Data\HiFi\ASA\Weather\current_wx_snapshot.txt file:EHAM::EHAM 120025Z 01004KT 9999 FEW040 13/11 Q1031 NOSIG::EHAM 120443Z 1206/1312 36005KT 9999 SCT020 SCT040 BECMG 1206/120902010KT PROB30 TEMPO 1206/1209 7000 -SHRA SCT008 FEW018CB BKN020::040,020,09.8/040,023,06.8/035,022,07.0/009,022,-01.5/011,037,-12.2/013,046,-22.4/016,066,-36.8/016,071,-47.8/030,081,-60.0However these is no EHAM entry in the 'current_synthesized_wx.txt' file (Dunno if this should be however...)

Don't you have "maximum surface wind" set at 0 kts in that picture of ASA? Perhaps that'll turn off ASA's downloading of surface winds, why bother when you won't be using surface winds anyway?

Don't you have "maximum surface wind" set at 0 kts in that picture of ASA? Perhaps that'll turn off ASA's downloading of surface winds, why bother when you won't be using surface winds anyway?

Yes.....Hence my remark during the 2nd test: "I tested this morning again with the same result, after having set the max surafce winds to 50kts in ASA

Oops, missed that one. I don't know what else it can be. WideFS working properly?

Hi All,Let me drop Damian a note about this.Thanks,

I know that problem too. Only after starting ASA & FSX.But ASA fixes that after a few minutes standing on the ground.

Hi,And tonight when I checked I do get winds and current data at EHAM and the whole area has correct winds and up to date data. It could have been a data issue along the line somewhere.Thanks,

I just reinstalled ASA, thought I'd give it and the final SP1 another try. I'm also getting these 225/0 reports for a variety of airports, EHAM among others, although not all of them. This is a fresh install of ASA + SP1 and I'm using FS9.It's problematic as I fetch reports to aid in flightplanning and Afcad choices, before running FS.Edit: started the sim, let the sim run for a while and no change. Tried refresh AI, regular refresh, time change, no change. Closed the sim, did a manual weather download and only then did the report display the correct wind, 030/16. Closed ASA, restarted it, when it was finally finished, the report said... 225/0.

Hi all, it's the same problem I have when WX are interpolated, wind is reported as 225/0. The only solution I've found so far is to launch ASA first, then FSX/9. I know Jim always says to do that, but I'd rather fire up the sim, set it the way I want, then when I'm ready launch ASA, especially if I want to use historical wx. Try loading ASA before the sim, it should be ok.CheersFede

I always start and let settle ASA/ActiveSky before running the sim. Same with the experiences from my previous post, ASA was started first if applicable.

Hi All,I did write Damian about this and there was a problem with one of the servers which has been fixed. This is why sometimes restarting AS seemed to fix the problem because then AS connected to the server that was not experiencing the issue.Things should be OK now.Thanks,