Just for the record, I am having the same issues as the OP, ATC directs planes to the opposite runway. I have not really found the cure for this. So far it helped pretty much not to import a flightplan. I have DWC checked and DRC set to 0. Will try 50%. Build 572.Also, Amsterdam EHAM is where most of my flights begin. When on the ground I also use SHIFT Z to check the wind. When on the ground I see wind shifts from 240 to 040 and back in 2 minutes. I get the impression that ASE has a problem setting the wind. Since EHAM has a very complex set of runways these radical wind shifts can result in planes landing 18 and others on 36. Just depends on when they ask ATC for clearance and whcih wind direction is valid then.Jim, just go to EHAM and check the wind with SHIFT Z. Menno

Just for the record, I am having the same issues as the OP, ATC directs planes to the opposite runway. I have not really found the cure for this. So far it helped pretty much not to import a flightplan. I have DWC checked and DRC set to 0. Will try 50%. Build 572.Also, Amsterdam EHAM is where most of my flights begin. When on the ground I also use SHIFT Z to check the wind. When on the ground I see wind shifts from 240 to 040 and back in 2 minutes. I get the impression that ASE has a problem setting the wind. Since EHAM has a very complex set of runways these radical wind shifts can result in planes landing 18 and others on 36. Just depends on when they ask ATC for clearance and whcih wind direction is valid then.Jim, just go to EHAM and check the wind with SHIFT Z. Menno

Menno, mine is acting better since I:1. Turned off DWC and Visibility Smoothing2. Set the Dyanamic Rate of Change slider im ASE to 100%3. Turned off the turbulence/thermals box in FSXThe winds still dont match perfect but a lot closer, the arrival winds in FSX are still off by about 10 to 15 degrees, but at least not off by 180 degrees like they were before.Today I am going to test changing by FSX.cfg lines MinVarTime and MaxVarTime both to "80" as per this post in the ASE forum: http://www2.hifisim.com/node/1243

Hi Sean,Thats good news. If you want an exact weather match at the destination, this thread has some fsx.cfg tweaks that are susposed to fix it. I'm still testing these myself, but it does appear to have some merit.http://www2.hifisim.com/node/1243Best wishesSteve

Hi Steve. I just tried those setting of 80 in the MinVarTime and MaxVarTime, but they didn't make any difference, so I reset them back to 5 and 50 which is what my stock settings were.Although ASE is matching up better, it's still not prefect. Today I did a flight from SBGL to SBGR and at SBGR ASE reported winds 180 at 5 kts, while FSX was reporting 197 at 5kts. When I departed SBGL ASE reported winds of 300 at 5kts while FSX reported 280 at 6.Everything seems to be matching up pretty much exactly except the winds. Altough when I landed at SBGR ASE said the ceiling was 1100 feet, but when I got there there were clouds on the runways and terminals.Frankly, I don't think anyone including the nice folks at HiFi really know how to get this thing to sync ASE and FSX excatly or what the problem is. If they do know I wish they could come forward. It would be really nice to hear from Damien who is the programmer and see if he has any suggestions.I haven't heard anything back from Jim in the past day, so I am not sure if that means he has nothing else to add or if he frankly just doesn't know?

Hi,I watch and read every single post! When users are sharing information and experimenting, I just read things. Only if there would be wrong information shared would I step in.What you are not taking into account with you latest examples is that FS reports magnetic direction of the winds and AS reports the real direction. So now, SBGR was 197 in FSX so you take the Magnetic Variation of the station, -20 into account and FSX has a real wind direction of 177 and ASE was reporting 180. Those are the same.SBGL right now is reporting 260@9 in ASE and 280 in FSX. The magnetic variation is -22 so 280 minus 22 gives us 258 which is the same as 260.So in both of these specific examples FSX and ASE were/are matched up.

Hi,I watch and read every single post! When users are sharing information and experimenting, I just read things. Only if there would be wrong information shared would I step in.What you are not taking into account with you latest examples is that FS reports magnetic direction of the winds and AS reports the real direction. So now, SBGR was 197 in FSX so you take the Magnetic Variation of the station, -20 into account and FSX has a real wind direction of 177 and ASE was reporting 180. Those are the same.SBGL right now is reporting 260@9 in ASE and 280 in FSX. The magnetic variation is -22 so 280 minus 22 gives us 258 which is the same as 260.So in both of these specific examples FSX and ASE were/are matched up.

Hi Jim, thanks for chimming in, I didn't know you were still observing, so my apologies if what I said came across wrong.How can I calculate the magnetic variation myself? The reason being is that at some airports the difference of 20 degrees can make a difference in what runways get used. Like at SBGR for example it has runways that face 09/270 degrees, so 180 degrees is the point that sepereates traffic from landing east or west. Like if the winds are from 190 in ASE you would assume to take runway 26, however if you take 20 degrees off off that then you get 170 and will probably be landing on runway 09.Basically in the end I guess it boils down to just being able to figure out in advance which runways I will be expecting. Going forward I guess I could open the FSX map up when I am about 100 mile out and check the wind on it, but if possible I would like to just go off of what ASE says.Also if I am flying in other parts of the world, how do I know how much magnetic variation to add or subtract from the winds to know what FSX will be showing?ORIs there a way to get ASE to display the winds with magnetic variation built in so that it will more closely relate to FSX'es weather stations?Thanks in advance.SeanPOST EDIT:I just found an entry in the FSX.cfg in the [Weather] section that says: AdjustForMagVarInDialog=1 . If I change that to 0(Zero) will that make it sync up closer to ASE? While I am waiting I will give it a shot.

Also if I am flying in other parts of the world, how do I know how much magnetic variation to add or subtract from the winds to know what FSX will be showing?

Never mind this question. I just saw in the ASE Briefing area where a flight plan is that it has a column for magnetic variation.

Hi,I watch and read every single post! When users are sharing information and experimenting, I just read things. Only if there would be wrong information shared would I step in.What you are not taking into account with you latest examples is that FS reports magnetic direction of the winds and AS reports the real direction. So now, SBGR was 197 in FSX so you take the Magnetic Variation of the station, -20 into account and FSX has a real wind direction of 177 and ASE was reporting 180. Those are the same.SBGL right now is reporting 260@9 in ASE and 280 in FSX. The magnetic variation is -22 so 280 minus 22 gives us 258 which is the same as 260.So in both of these specific examples FSX and ASE were/are matched up.

I didn't know that, now it all becomes clear! :( Sean - I have had some success with those tweaks, although I was using 100, but having just read the above, perhaps it was more fluke (low mag var) than the twak actually doing anything :(

I didn't know that, now it all becomes clear! :( Sean - I have had some success with those tweaks, although I was using 100, but having just read the above, perhaps it was more fluke (low mag var) than the twak actually doing anything :(

Yeah your probably right and that explanes why sometimes the winds in FSX seem to be matching up with ASE and sometimes they seem to be 20 degrees off.Frankly I wish Jim had told me this from the start, but maybe he though I already knew. Going forward if anyone else posts about the same thing it could be due to the magnetic variation.Good info to have.

Hi All,The Mag variation is always listed on the Report Screen, near the top, under Position. You take this value and add it to the Shift/Z readout from FS. Please remember that when adding a negative value is the same as subtraction.

Hi All,The Mag variation is always listed on the Report Screen, near the top, under Position. You take this value and add it to the Shift/Z readout from FS. Please remember that when adding a negative value is the same as subtraction.

Jim, would it be possible in the next update to get an option to have the winds displayed in ASE with the magnetic variation built in rather than the true direction?

Hi,No, the real world data format is true direction. It is MS that has had it wrong for all these years!

LOL, gotcha.

Menno, mine is acting better since I:1. Turned off DWC and Visibility Smoothing2. Set the Dyanamic Rate of Change slider im ASE to 100%3. Turned off the turbulence/thermals box in FSXThe winds still dont match perfect but a lot closer, the arrival winds in FSX are still off by about 10 to 15 degrees, but at least not off by 180 degrees like they were before.Today I am going to test changing by FSX.cfg lines MinVarTime and MaxVarTime both to "80" as per this post in the ASE forum: http://www2.hifisim.com/node/1243

Sean, the changes seem to work here too. Menno

Sean, the changes seem to work here too. Menno

I am sorry to say that the new release did not solve the rapid wind changes resulting in the destination winds very often leading to wrong runway assignment.Leaving VHHH winds were reported 070@5. However ATC used both runways, 07 and 25 because the winds shifted dramatically. On arrival, the 15:28h ASE weather report of ZSPD yesterday showed winds 055@5. That would lead to runways 34 and 35 in use. Indeed ATC used 34 for take off but 17 for landing. When on the ground SHIFT Z showed winds changing from 340 to 135 thus explaining the strange ATC assignments.Some happened at KDFW. Winds reported were 140@6. Runways in use (simultaneously) were 18 and 36. Again, SHIFT Z showed the wind was changing rapidly, almost showing a 180 degree difference in direction.I have also reported this in EHAM. Hence, this must be an ASE issue, apart from any magnetic variation.Menno

Hi,The same thing for me, for example when the wind is 350v070 the wind shown in fs9 is about 220 and not something between 350 and 070 in fact it is the opposite.On the other hand if the metar is 010v100 the wind shown in fs9 is correct so in my opinion there is a problem when the wind varies from 3xx to 0xx in FS9.Thanks,Christian