hi,I had my destination locked for LSGG(60 nm) and the locked METAR and ATIS were reporting winds wich would have runway 23 as the active one (and not runway 5) ,yet I was vectored for ILS runway 05 ,which is very strange because sides have ILS,so no side is favoured and like I said winds were coming from ca.250of course I was told to do a circling appraoch to runway 23 by the tower.I found this to be very strange because all indications were pointing that I should have been vectored to runway 23 and destination was locked.Could this have something to do with winds aloft,because it was only center and approach that assigned me runway 05,tower was sending departures to 23,so it has nothing to do with surface winds I guess

Seba,This appears to be a problem that several of us are experiencing. What other add-on programs are you using simultaneously with ActiveSky? Dave Vega

I experience the same anomoly as Seba. Each time I am handed off by approach to tower, tower always instructs a downwind to the opposite runway. This is kinda annoying since you are on (or nearly on) the glide slope by the time you are handed off to tower frequency and now you must abort your ILS approach and fly a left or right downwind to another runway. The only other program running with ActiveSky is MSFS. In fact, I use "End-it-all" before using the sim. Anyone knowing the work-around for this would be appreciated.Thanks

I lock my destination about 100nm out. It seems FS ATC chooses a final vector based on the weather about 60nm out. So just to be safe try extending your destination lock to more than 60nm.Works for me!

Thanks, will give that a try!

I lock at 70 miles and I don't get those problems.

I've had mine locked at 75nm and the issue persists. I'm going to try the 100nm, but this begins to reduce the realistic nature of dynamic weather (i.e. flying into an area with numerous microclimates, etc.).The latest example was: departing MMMX for KSAT. I was sent to the departure runway 5L. Followed a departing American 737 to Miami, I left the radio tuned to the Tower frequency as I climbed out and turned north. As I passed 10 miles out, I hear a Mexicana arrival, inbound on the visual 5L. He was then vectored by ATC to 23L. Of course, AI has no idea what to do after getting the conflicting runway assignment, and it promptly puts the plane down on the originally stated runway (even though they acknowledge the change to ATC)Nearly every flight I've flown since installing ActiveSky wxRE, IFR or otherwise, upon arrival, ATC vectors me to another runway. Real fun, as I usually pick the my destinations based on where the worst weather is... Comments?-b

I've tried values between 60nm and 100nm with no real change with the problem either. In fact, last night with the lock value set to 70nm I had TWO rwy changes approaching Hilo Intl from PHNL. My original vector was for a rwy 8 approach, which I was forced to go around for because ATC tried to fly me through a mountain on approach and I couldn't get (realistically) low enough. ATC then vectored me for a rwy 26 approach, which was all going just fine and dandy until the tower handoff and, you guessed it, fly left downwind for a rwy 8 approach Sir! At this point, my 10 failures per hour on my 767 PIC were approaching critical mass for flight safety, so I decided to land on rwy 26 against ATC instructions. Amusing at times, however I too would like to see this problem rectified in a near future release of ActiveSky WxRE.Gary

Do you guys have the "Update METARs on New Station" option enabled?If so deselect that option and try it again. Like I said earlier, i have my Lock set at 70 miles and I've never had this problem.