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.

Different altimeter ...

Featured Replies

Hello Jim, hello Damian, hello folks !I have lately witnessed a strange behavior from AS6.5 running with Fs9 from a networked client.Listening to the ATIS, everything but the altimeter is correctly reported like shown by the AS window.If I look at the METAR showed for the closest station on the ASKy window, I find that all settings read by ATIS match the Metar, except the altimeter ...Anyone else ever reported this ? Eugenio.P.s. also, I noticed that the different altimeter happens to be almost 99,9 % of the times the value provided for the destination airport of a (imported) FS flight route, instead that for departure. Strange, eh ?

I too have started experiencing this problem. I can see the altimeter gauge in my aircraft jump on initial setting, but then it resets to 2992. All weather settings are off in FSUIPC and AS has "force through FSUIPC" set to on. Any clues?-Rick

It seems to happen while on the ground. And I don't have "disable all updates on ground" active. Just the one that stops the update after initial weather set. AS seems to go active while FS is sitting at the main screen rather than waiting until FS is ready. And I have Ignore ready status off and start paused on. If I exit OUT of AS and come back into it after FS is loaded and I'm in the cockpit, it seems to do ok. It's not in a refresh cycle. I'm running build 552, which is the last one I've seen. FSUIPC is 3.80 and I'm running WideFS (altho AS is on the same computer as FS and doesn't use it) and both are registered. Running Vista Home Premium (32-bit), FS/AS on a AMD64 dual-core with 4gig of memory. Think that wraps it up. Hopefully this helps as it's driving me nuts.-RickBTW, I'm using GEPro with AS as well.

I figured you were just checking the FSReady variable to determine that. I'm also going to use the Weatherset program that comes with FSUIPC to see if it does the same thing. Anyway, here's my INI//ASv6.5 configuration file Build 552[General]WindowPosX = 975WindowPosY = 555DefaultWeatherFolder = D:fs2004ModulesASv6SuppressionCeiling = 10000SurfaceWindLimit = 10FS9Path = D:fs2004PersonalAppDataFolder = C:UsersOwnerAppDataRoamingCloudLayerLimit = 5LocalSuppressionRange = 100MinimumVisibility = 0MaximumVisibility = 59AutoVasFrequency = 30AutoVasStrength = 30TurbulenceFrequency = 50DefaultStartupLocation = KSEADefaultGraphicsFullTheme = Wx-InfluencedDefaultGraphicsCirrusTheme = Wx-InfluencedAutoSubmitGraphicsTheme = TrueIncreasedWake = FalseDisableWindsAloft = FalseForcePrimaryServer = FalseForceSecondaryServer = FalseGEProAutoSubmit = TrueUseFetchedStationforGEPro = TrueShowDecodedMBasDecimal = FalseSkyOverride = GEPROFavorCumulus = FalseForceRoutePressure = FalseForceLowestCeiling = FalseUnpauseOnReadyStatus = FalseDisableWriteThrottle = TrueDisableProcessThrottle = TrueForceTstormsWithCB = TrueAutoSetFSTime = TrueIgnoreFSLocationUntilReady = TrueAutoConvertPlanFiles = TrueAutoRefreshAI = TrueDisableVisGraduation = FalseEnableGEProWideFSMode = FalseExtendedThrottling = FalseForceRouteAloftTemp = FalseOfflinePlayback = FalseEnableVAS = TrueAutoGenVAS = TrueForceDestinationWeatherZone = FalsePreventIcing = TrueOnlineUpdates = TrueExtendedDestinationWindsForce = FalseDisableAllGroundUpdates = FalseGlobalWrites = FalseDepictFS9HazeLayer = TrueExtendTstormLayers = FalseDisableDirectWindControl = FalseVoicePlayback = FalseLocalSuppression = TrueStartupSound = FalseDisableGroundUpdates = TrueUseProxyServer = FalseFogLayerGeneration = TrueUpdateSuppression = TrueOvercastEnhancement = TrueIgnoreFSReadyStatus = FalseFSUIPCWindSmoothing = TrueLimitSurfaceWinds = FalseLimitCloudLayers = TrueAutoGlobalWriteToggle = TrueRainWithTS = TrueDisableUpperLayerGeneration = FalseVisibilitySmoothing = TrueDisableMessages = TrueAutoTimeZoneDetection = TrueUpdateInterval = 10VATSIMData = FalseZuluConversion = -7AloftPredictability = 100WindDriftRate = 0MaxCloudThickness = 10000MinStratusSeparation = 7000TAFProcessing = TrueEnforceVisibilityLimits = TrueWakeTurb = FalseStartPaused = TrueUseSystemTime = TrueDisableCAVOKClouds = FalseProxyAddress = NONELastPlanFolder = C:UsersOwnerDocumentsFlight Simulator Files-Rick

  • 2 weeks later...

Hi Jim.I have unchecked ALL the features provided in the upper left section of the options menu, and made sure that FSUIPC has no influence on wxr, but the strange behavior is still there: the altimeter at departure airport is not set to the value I see on the METAR referring to this airport, but rather to the value reported for the destination airport of a loaded flight plan, whose METAR I fetch and check before importing the whole route.One factor I need to mention here, is that I recently changed my flight planning program from FSNav to Flight Sim Commander: the latter is also able to generate flight plans in FS9 compatible format, which I load from within FS and from within all other addons who need it, including AS6.5.Might this be something to look at ?Thanks and regards,Eugenio.

I will, but I've already left home now ...The impression I had about the "disturbing" flight plan was reinforced, though: last night I ran FS and AS, I was in Nurnberg (EDDN), and upon first contact the wxr generated by AS within FS was coherent with the METAR for the closest station (EDDN).I got the confirmation by listening to both the local FS ATIS and to ActiveSky Service (on frq. 122.00).Then I fetched the wxr for my destination, that was Innsbruck (LOWI), and it displayed that METAR, with a different altimeter value.I used that info to pick up the right runway and set up my flight plan with FlightSim Commander, then saved the file in .pln format for FS use.I imported that flight plan in AS and - tadah ... - the altimeter for EDDN soon changed, and it became - guess what - the same altimeter value shown for LOWI ...This gave me this sensation of possible "confusion" by ASky ... how can this be ?Stay tuned, I will post the .ini file soon (tonight or tomorrow morning)Eugenio.

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.