I have experienced similar difficulty with weather not updating until I am on final. Two points to note:1. ASE (even with the new build) claims to be updating all weather stations very frequently, but the FSX map shows that only the stations closest to the current position (of the plane) agree with ASE wx. I have tried "additional stations" and "enhanced route coverage" and with different dynamic change settings. Though this seems to expand the radius of correct wx reports and definitely eliminates incidences of FSX changing to default wx in between stations, it still does not set destination wx correctly until I am on approach.2. Winds at 3000 ft agl can be quite different from the surface winds. This is realistic. Sometimes the wind can "clock" around 180 degrees during that last 3000 feet of approach. That should not be the issue. (Check what the winds are supposed to be at 6000 and 3000 for the destination airport on the ASE WX Change page.) ATC, however, must know the correct SURFACE wind at the destination airport in order to assign the correct runway. ASE is definitely inputting the information to FSX (according to the cfg files), but even with "force destination" or the extreme case of setting the application range to "global", FSX is not updating the destination weather until the aircraft is very close. This must be something with the FSX weather generating engine that ignores wx updates farther than a certain radius of the plane's position. FYI, in real life, ATC seldom assigns landing runways to aircraft 80 nm away!CraigFSX Deluxe, SP2, Quad Core 2.66Ghz, 4G Ram, 1G Nvidia 9500 GT, VISTA 64

I turned dynamic changes to 0% and things are better. But still not updating everything so well. Now I get cloud formations popping in my view so close, as in 5 or less miles away. this never happened before. Like the poster above, it must not be updating everything around my route properly, only the closest station at that present time.

So is there a conclusion to this or not?I'm using 122.02 to get destination weather to set my approach only to find that when I do get to FSX ATC they assign a different runway, which actually turns out to be correct based on the wind in the FSX ATIS.I had this with ASA actually but always assumed it was FSX which was assigning a tailwind landing, but it isn't!

I'm using fs9, registered fsuipc and was flying the pmdg md-11 into miami today when i had the same problem. while on approach and landing the winds (indicated by "shift + z") remained according to ase but the atis said winds roughly 180 degrees off.i uploaded a picture for an explanation. also i was checking the atis of ft. lauderdale (kfll) and it the atis was off by 180 compared to asethanks,Joseph

I have been trying to remember to refresh AI at the start of evry flight.It's early days but I think that maybe helps the problem at least.

I have been trying to remember to refresh AI at the start of evry flight.It's early days but I think that maybe helps the problem at least.

Thank you.Now, I ask HiFi a comprehensive list of settings to make good use of ASE, waiting for a SP.Settings:- ASE- FS9- FSX- FSUIPC (registered and unregistered)

Hi All,Please make sure you are using the AI Traffic Refresh Icon once ASE and FS are loaded.Nemo,Not sure what SP means, but for settings:ASE: default settingsFS9: 3D clouds 100% and cloud coverage maximumFSX: 3D clouds and cloud coverage maximumFSUIPC both registered and unregistered: Default settings and weather settings off.

Hi All,Please make sure you are using the AI Traffic Refresh Icon once ASE and FS are loaded.Nemo,Not sure what SP means, but for settings:ASE: default settingsFS9: 3D clouds 100% and cloud coverage maximumFSX: 3D clouds and cloud coverage maximumFSUIPC both registered and unregistered: Default settings and weather settings off.

Jimis not true.FSUIPC works best with FS clock sync on.However, this option can be activated only with registered copy.

Hi All,Please make sure you are using the AI Traffic Refresh Icon once ASE and FS are loaded.Nemo,Not sure what SP means, but for settings:ASE: default settingsFS9: 3D clouds 100% and cloud coverage maximumFSX: 3D clouds and cloud coverage maximumFSUIPC both registered and unregistered: Default settings and weather settings off.

Hi Jim - just to confirm....FSUIPC select default settings and wxr settings off will disable any wind/baro/turn smoothing via FSUIPC so I am going to need DWC (ON) in ASE? I was initially using DWC ON and FSUIPC wxr = OFF...but found I still got wind spikes in ASE so I turned DWC OFF and went with FSUIPC smoothing for turb, winds, and baro.

I'm having this problem also. On a flight earlier today, the winds at KBOS were 110 at 14 kts. ATC had me land on runway 33L. I am using DWC, and not using FSUICP. I hope this problem can be resolved shortly.

ACA,That is all correct, but what I can suggest is that you re-set things and then go back into FSUIPC and re-enable your smoothing options.Curt,Did you refresh the AI system after AS and FS were up and running?

Hello,i can confirm that the weather (especially wind direction/speed) on final is different than the destination METAR during 80% of my approaches (FSX). I

ACA,That is all correct, but what I can suggest is that you re-set things and then go back into FSUIPC and re-enable your smoothing options.Curt,Did you refresh the AI system after AS and FS were up and running?

Yes, and I tried another flight today on the same route into KBOS. Winds 110 at 12, but ATC always has me and the AI traffic landing on 33L.

Hi Curt,Is ASE Build 572?

Hi Curt,Is ASE Build 572?

Yes it is, and as someone else pointed out the departure airport is always correct, only the destination has problems.