I'm sorry if this has been asked before but is there any kind of setting in ActiveSky that can minimize (or prevent) the plane from going to OVERSPEED situations anytime the weather or wind changes above FL210? I'm using the latest build (142?)and I'm using the FSUIPC that came with it. Do I need to buy the registered version?Thanks.

Hi Steven,You should be using NORMAL DEFAULTS in AS2004.5 (namely, FSUIPC Wind Smoothing Enabled). This will provide standard FSUIPC wind smoothing of 5kts/deg per second max change. Assuming you are not flying dangerously close to Vne/Vmo (within 15kts or so), you should never get an overspeed due to a wind transition.The registered FSUIPC will give you the ability to change the 5kts/deg value to something smaller, so that changes happen slower. This may be what you desire but I believe the normal unregistered defaults, when using proper speeds, should yield proper and realistic results.Hope that helps!

Hi Steven,To add to what Damian said you cannot fly at the "barber pole" and not expect overspeeds. You may need to slow down just a bit!Hope this helps,JimActiveSky Supporthttp://www.hifisim.com/images/as2004proudsupporter.jpg

Thanks, you two. Great product, by the way.

As I compose this, I am flying from PANC to KDEN on my other computer. I am using B142 and this is the 1st problem I've had. I'm at FL410 in the KH737-800 at .8M. Flying along nicely and have gotten 4 Overspeeds, where the a/c goes from .8M to .9M, back down to .7M. Have had to disable a/t til a/c slows down, then reable. I can see the winds shifting slowing as they should. It seems though that the weather was updating at the time of the overspeed, i.e. the green text bar was on the screen at the time.Rick

Hi Rick,If you have the pay version of FSUIPC then you may need to increase the wind smoothing. If not, you may need to slow down a bit.Hope this helps,JimActiveSky Supporthttp://www.hifisim.com/images/as2004proudsupporter.jpg

Hi Rick...That is strange! A change of .1 mach (probably ~20 KIAS depending on alt and temps) is not normal when wind smoothing is enabled.I'm not sure the update has anything to do with it. The green scroll text occurs approximately 15 seconds AFTER an update completes. Remember that actual wx condition updates around your local area do not normally occur anyhow due to local suppression.Hmmm... perhaps this is due to a temperature shift instead of a wind shift? Do you note any temperature oddities when this problem occurs?To help isolate:If you have registered FSUIPC please try slowing down the wind changes to see if that solves the problem. You also can try disabling Direct Wind Control as it may be related to that feature.Have you had success with B142 up until this point, or has B142 always had this problem for you?Thanks for the information!

Utilizing build 142, I too have experienced overspeeds and abrupt wind direction changes (20 degrees or so) aloft UNLESS I have the extended wind smoothing options enabled with my registered version of FSUIPC. For me personally, a registered version of FSUIPC is the only way to reign in the winds aloft smoothing problem once and for all.

This is the first time I have had any problem with b142. As I said it happened 4 times during this flight, and appeared to take place just after a weather update over unpopulated areas of Alaska & Canada. Iwas not looking for temp changes, so I can't answer that question. I couls see the wind arrow & speed changing on my panel, but it was changing a few derees & kt every sec. or so, like it should. For some reason, it disrupted the autopilot like it used to before all the beta releases. I also have the registered version of FSUIPC.I fly for 2 VA's, so I fly a lot of high altitude flights and this is a 1st for b142. Could it have something to do with remotely populated areas? I don't remember seeing th a/c get buffeted around like before the pre MR2 release, when the airspeed would jump all over the place on wind shifts. How much of a temp change would hace to occur to cause problems?For the most part, b142 has been rock-solid. As this was a 4.5 hr flight, I had my back turned when it first happened. I couldn't believe I was hearing the "OVERSPEED" alarm. But I do know that when the problems were happening, everytime, the green text was on the screen.I will fly again tonight, and watch more closely, and try to observe more, if it happens again! ps Could any of my settings have caused this to occur.....I haven't changed any from when I started using b142, and thats been over 1 week, and have flown at least 7 flights over that period with no problems!Rick

Hi Dianne,Were you able to confirm that the wind direction changes at default 5kt/deg per second are indeed working correctly? Thus the 5kts/deg is simply too quick a rate for the smoothness you require?Or is the FSUIPC wind smoothing failing entirely, instantly changing direction more than 5deg/kts per second?Thanks!

Hi Rick,Yes it could be related to low-density reporting areas and significant changes in local weather - because local suppression is limited in such areas due to FS9 interpolation. It could be the temperature and/or pressure causing air density changes and subsequent airspeed changes.You may wish to use global writes (disable auto global toggle and check global writes) in such areas to help. Increasing the local suppression range can also help (try up to the max 150 miles).If you can duplicate such significant changes in speeds please save me a wx file and send to [email protected]. I'll attempt to duplicate...Thanks!

I had a similar occurance tonight. Flying from KTUL to KDEN, I was climbing through FL240 up to FL350, when it started raining when there were SCT clouds about 10,000 feet below me. No mention of rain in any Metar's or forecast either. All of a sudden you hear the engines start to increase and watch the speed go up over .8M and I was at about .64M in the climb. I was flying a different a/c from the previous problem and the overspeed happened just after the rain started at FL240.Rick

Hi Rick...Hmmm.. let's take a look at that as2004.ini just to confirm all the settings.. thanks!

Damian,Here's a copy of my ini file.Rick//AS2004.5 configuration file Build 142[General]WindowPosX = 4965WindowPosY = 2895DefaultWeatherFolder = E:FlightSimsfs2004ModulesActiveSky2004SuppressionCeiling = 4000SurfaceWindLimit = 10CloudLayerLimit = 5LocalSuppressionRange = 100MinimumVisibility = 0MaximumVisibility = 70IncreasedWake = FalseDisableWindsAloft = FalseForceTstormsWithCB = FalseAutoConvertPlanFiles = TrueForceDestinationWeatherZone = FalsePreventIcing = FalseOnlineUpdates = TrueExtendedDestinationWindsForce = FalseGlobalWrites = TrueDepictFS9HazeLayer = FalseDisableDirectWindControl = FalseVoicePlayback = TrueLocalSuppression = TrueStartupSound = FalseDisableGroundUpdates = FalseUseProxyServer = FalseFogLayerGeneration = TrueUpdateSuppression = TrueOvercastEnhancement = TrueIgnoreFSReadyStatus = FalseFSUIPCWindSmoothing = TrueLimitSurfaceWinds = FalseLimitCloudLayers = TrueAutoGlobalWriteToggle = FalseRainWithTS = TrueDisableUpperLayerGeneration = FalseVisibilitySmoothing = TrueDisableMessages = FalseAutoTimeZoneDetection = TrueUpdateInterval = 50VATSIMData = FalseZuluConversion = -5AloftPredictability = 100WindDriftRate = 0TAFProcessing = TrueEnforceVisibilityLimits = TrueWakeTurb = FalseStartPaused = TrueUseSystemTime = TrueDisableCAVOKClouds = FalseProxyAddress = NONELastPlanFolder = C:Documents and SettingsOwnerMy DocumentsFlight Simulator Files

Hi Rick,Thanks for that..Here is my theory: The global write process (either by using it forced on, as in your current settings, or when using auto global toggle and flying in sparse areas) is activating erroneously during your flight (it should only happen when on the ground, before your flight). To confirm this, in your above example if you turned off global writes the problem should cease during updates. If you could test this it would be much appreciated. Next time it starts occuring during updates, turn off global writes, and test (please also post the as2004.log at this point). If the problem stops, re-enable global writes and test again, it should start happening again.As to why global writes would be occuring during the flight, I don't know, it certainly is not supposed to but may be related to other changes. Let's see if we can isolate and confirm this as the problem and I'll examine the code...Thanks for your help and patience!