Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Force Destination Wx not working

Featured Replies

1. On route KPDX to KSFO just now this is the metar for KSFO:KSFO 310256Z 19019G26KT 6SM BR SCT020 BKN025 OVC042 16/14 A2979 RMK AO2 PK WND 19029/0233 RAE14B31E46 CIG 013 RWY L10 SLP089 P0002 60005 I used force destination weather, but along the approach via PYE to 19L despite the very poor weather predicted by the METAR I had great vistas of the City Of San Francisco and Oakland,(obvioulsy within a few miles of the airport) although it was a bit hazy the sky was mostly clear. It was not until nearly at the runway ( a couple of miles out) that I began to see any real clouds.I remember this lack of forced destination weather being an issue with earlier version of Active Sky that got fixed.I did put in the route KPDX-KSFO into ASV6.2. One other unrelated thing. I have flown many hours with weather influenced Cirrus theme, but have yet to see a single cirrus cloud generated.This is my ini file. Perhaps some combination of settings defeats the force destinaton weather?//ASv6 configuration file Build 446[General]WindowPosX = 2445WindowPosY = 540DefaultWeatherFolder = D:Program FilesMicrosoft GamesFlight Simulator 9ModulesASv6SuppressionCeiling = 20000SurfaceWindLimit = 10FS9Path = D:Program FilesMicrosoft GamesFlight Simulator 9PersonalAppDataFolder = C:Documents and SettingsGregoryApplication DataCloudLayerLimit = 5LocalSuppressionRange = 100MinimumVisibility = 0MaximumVisibility = 59LastPlanFolder = C:Documents and SettingsGregoryMy DocumentsFlight Simulator FilesAutoVasFrequency = 30AutoVasStrength = 30TurbulenceFrequency = 30DefaultStartupLocation = KSEADefaultGraphicsFullTheme = Greg's IGS Theme NO Sky ChangesDefaultGraphicsCirrusTheme = Wx-InfluencedAutoSubmitGraphicsTheme = FalseIncreasedWake = FalseDisableWindsAloft = FalseForcePrimaryServer = FalseForceSecondaryServer = FalseFavorCumulus = FalseForceRoutePressure = FalseForceLowestCeiling = TrueUnpauseOnReadyStatus = FalseForceTstormsWithCB = TrueAutoSetFSTime = FalseIgnoreFSLocationUntilReady = FalseAutoConvertPlanFiles = TrueAutoRefreshAI = TrueDisableVisGraduation = FalseForceRouteAloftTemp = FalseOfflinePlayback = FalseEnableVAS = TrueAutoGenVAS = TrueForceDestinationWeatherZone = TruePreventIcing = TrueOnlineUpdates = TrueExtendedDestinationWindsForce = TrueDisableAllGroundUpdates = TrueGlobalWrites = FalseDepictFS9HazeLayer = TrueExtendTstormLayers = TrueDisableDirectWindControl = FalseVoicePlayback = FalseLocalSuppression = TrueStartupSound = TrueDisableGroundUpdates = TrueUseProxyServer = FalseFogLayerGeneration = TrueUpdateSuppression = TrueOvercastEnhancement = TrueIgnoreFSReadyStatus = FalseFSUIPCWindSmoothing = TrueLimitSurfaceWinds = FalseLimitCloudLayers = FalseAutoGlobalWriteToggle = TrueRainWithTS = TrueDisableUpperLayerGeneration = FalseVisibilitySmoothing = TrueDisableMessages = TrueAutoTimeZoneDetection = TrueUpdateInterval = 10VATSIMData = FalseZuluConversion = -8AloftPredictability = 100WindDriftRate = 0MaxCloudThickness = 10000MinStratusSeparation = 7000TAFProcessing = FalseEnforceVisibilityLimits = TrueWakeTurb = FalseStartPaused = FalseUseSystemTime = TrueDisableCAVOKClouds = FalseProxyAddress = NONEThanks,Greg

Greg Clark

  • Commercial Member

Hi,As for force destination, KSFO has been reported/confirmed before as being problematic... for some reason the depiction just doesn't show sometimes even though every airport within 80nm is being forced to the conditions of the destination. This is most likely due to interpolation routines within this area internally coded inside FS9, or an issue with the wx stations in the FS9 station database coupled with certain wx conditions. It has been reported that decreasing the update interval (try 5 minutes) can help. There are a few other airports (maybe 3 or 4) that have been reported to exhibit this behavior as well. Force destination unfortunately does not always work as one might expect in a non-global weather environment. Needless to say, we're working on improving this potential situation by implementing a brand new related feature (more news soon).As for no cirrus, it could be because of ceilings.. by default we have enabled "force lowest ceiling" which will effectively eliminate any layer above a reported ceiling layer... The benefit in this is that you won't get higher clouds interfering with ceiling layers and possibly making them too thin (are rare occurance but it does happen, and this was a very popular request). The down-side is fewer cirrus opportunities in "ceiling" wx conditions. Ceiling means Broken or Overcast. Please try tuning this option off, it sounds like it may work out better for you...Hope that helps,

Damian Clark
HiFi  Simulation Technologies

  • Author

Thanks Damian! I always seem to stumble on those rare situations by dumb luck. RE: cirrus, I have been flying mostly in overcast conditions and that may account for the lack of cirrus. I will try the fix you mention and fly the same route with the same weather to see what it looks like.Your company shines in software development by listening to its customers and going way beyond by trying very hard to get around FS 9 limitations.Happy New Year!Greg

Greg Clark

  • Author

Very interesting. I unchecked force destination weather and force lowest ceiling and reflew the same flight using the same archived weather. Huge difference. (I assume due to not using force lowest ceiling). Much richer visual environment with multiple cloud layers, overcast reproduced more faithfully along the route, and the weather at KSFO and evirons was as expected per METAR. Did see cirrus as well.I will prefer to not use the force lowest ceiling option myself in the future, but glad the flexibility is there for those who want to use it.Greg

Greg Clark

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.