Hi Jim, Below is my .ini file.Like I said, I only have trouble with long flights, the winds start to go weird about 6 to 7 hours into a 9 or mor hor flight, about 3 hours or 1000 nm before the destination.I have absolutely no problems on shorter flights using the .ini setting below, wind smoothing works lie a charm from takeoff to touchdown on flights of less thatn about 4 hours.Best RegardsMax (Bern, LSZB)http://www.hifisim.com/images/as2004betateam.jpg http://www.precisionmanuals.com/images/forum/800driver.jpg//AS2004 configuration file[General]WindowPosX = 5160WindowPosY = 5205DefaultWeatherFolder = F:Program FilesMicrosoft GamesFlight Simulator 9ModulesActiveSky2004SuppressionCeiling = 2000SurfaceWindLimit = 10CloudLayerLimit = 5LocalSuppressionRange = 100MinimumVisibility = 0MaximumVisibility = 50IncreasedWake = FalseDisableWindsAloft = FalseForceDestinationWeatherZone = FalsePreventIcing = TrueOnlineUpdates = TrueExtendedDestinationWindsForce = FalseGlobalWrites = FalseVoicePlayback = TrueLocalSuppression = TrueStartupSound = FalseUseProxyServer = FalseFogLayerGeneration = TrueUpdateSuppression = TrueOvercastEnhancement = TrueRouteWindSmoothing = TrueLimitSurfaceWinds = FalseLimitCloudLayers = TrueAutoGlobalWriteToggle = TrueCCWindsFix = TrueDisableUpperLayerGeneration = FalseVisibilitySmoothing = TrueDisableMessages = FalseAutoTimeZoneDetection = TrueUpdateInterval = 10VATSIMData = FalseZuluConversion = 1TAFProcessing = FalseEnforceVisibilityLimits = TrueWakeTurb = FalseStartPaused = FalseUseSystemTime = TrueDisableCAVOKClouds = FalseProxyAddress = NONE

Hi Max,Settings look good. Now I wonder if it is the FACT wind station. If you fly into another station please post your findings.Hope this helps,JimActiveSky Supporthttp://www.hifisim.com/images/as2004proudsupporter.jpg

Hi,Max, thanks for your reports on this. As of now it seems related only to a certain area and when the flight exceeds several hours - is this correct?Part of the problem may be due to different global wx station densities over the course of the long flight. When the wind starts going unpredictable like this, it is FS9 taking over the wind layer and applying faulty values. When FS9 does this, there is no way to resume control of the wind layer until FS9 decides to 'release' it. Have you tried forcing global writes on or off (without autotoggle) with any effect? Have you tried without route-based wind smoothing enabled?I will try to replicate the situation with a very long test flight but I must admit it is very difficult for me to do so (time seems short these days!) and see if I can find anything. Will report back on that, but it may take a few days...Thanks again for your reports and thanks Jim for troubleshooting...-Damian

Damian (and Jim)Actually it's not related to a single area of the world. My first long range flight was a North Atlanric Crossing from Zurich to Atlanta (KATL), the second was to sotuh Africa.Of course it may still be related to station densities, because on the first flight the problems started shortly after making the first landfall over Nova Scotia where there may be few stations. There are also few stations in Africa, I presume, because the second flight took me south from switzerland making landfall in tunisia and then of course over a sparsely populated part of Africa. During both flight, the wind shifts eventually stopped and the wind dirs settled, but the winds were not matching the nav log or AS main window after that until I started the descent where for both KATL and FACT, winds would slowly rotate to match the arrival metar.I will try to recreate those same flights again with global writes set to on and again with wnd smoothing off.My assumption is still that the wind shifts are somehow related to the duration of the flights, because I had made several flights in Africa with the 737NG, but these were of course shorter, 5 hours max and even when flying into FACT I had none of those shifts, even though the route for a sizeable portion of the flight was the same as that flown on my long range flight to zurich.So I tought that maybe, since weather can change considerably in 10 hours, that somehow this was causing the wind shifts. On the long range flights I also had several cloud pop ups and pop aways during the later part of the flight, that I never have on shorter flights in the same area.Please note that I am still VERY happy with build 90, but maybe if we can somehow find out what causes the funny behaviour on long flights, there might even be an easy fix for the long range flight that would make AS 2004 even better than it already is. Best RegardsMax (Bern, LSZB)http://www.hifisim.com/images/as2004betateam.jpg http://www.precisionmanuals.com/images/forum/800driver.jpg

Thanks Max,And of course that is always our goal!Hope this helps,JimActiveSky Supporthttp://www.hifisim.com/images/as2004proudsupporter.jpg

I have been using MR1 "quietly" since it's beta release, and have been enjoying the results. I generally fly VFR in the Caribbean with no plan. But I do fly "seriously" for my VA and with the PMDGNG.I only rarely experience wil wind-shifts, but they do still occur (and once they start, they just won't stop). What I have found is (and this is completely anecdotal) that the more waypoints I have in my imported flight plan, the more likely the occurence of the crazy-wind phenomenon.I regularly fly a route from KLAS->KLAX, and it seems that if I leave out the DP and STAR waypoints out of the plan, I never experience crazy wind shifts. If I put them in, I get the wind shifts maybe half the time. HTH,

Same problem here on long haul flights:I flew yesterday from LEMD to EETN (Madrid-Talinn) with an PSS-A340. After about 2 hours (flying over Germany) severe wind shifts and baro variations made the flight very uncomfortable...I never experienced this phenomena on short flights with build 90 till now.RegardsJean-Claude(LSZH)

HelloJust to provide another information on the wind-shift puzzle for ActiveSky team - after a few weeks of happy and extensive ActiveSkying I have also experienced this problem when flying on VATSIM around UMMS ( that is Minsk, Belarus - and yes, the folks are running the VATSIM FIR there, go and check it ). The essential information as to what has happened can be viewed on the file attached.The flight itself was short, just 4 waypoints, total distance of less than 300 miles. Everything went smoothly up to the final approach, as shown in the attachement. and BTW that was my very first online flight to this area in East Europe ( I mean Belarus ). Not drawing any conclusions, just letting you know. Keep my fingers crossed for future development of your software & final fix for the problem.RegardsChrisP.S. AS v1.1 Build 90 aboard