Hello allFor some reason my destination weather only changes when I am about 2 miles from the airport (bit of a pain when online). I have added my config file for you to have a look at in case there is something I have overlooked.Gareth//ASV configuration file Build 367[General]WindowPosX = 495WindowPosY = 495DefaultWeatherFolder = C:Program FilesMicrosoft GamesFlight Simulator 9ModulesASVSuppressionCeiling = 15000SurfaceWindLimit = 10FS9Path = C:Program FilesMicrosoft GamesFlight Simulator 9CloudLayerLimit = 3LocalSuppressionRange = 50MinimumVisibility = 0MaximumVisibility = 59AutoVasFrequency = 40AutoVasStrength = AEStartupMode = 0IncreasedWake = TrueDisableWindsAloft = FalseDisableRandomLightSelect = FalseFavorCumulus = FalseForcePrimaryServer = FalseForceSecondaryServer = FalseFavorCumulus = FalseDisableRandomHaze = FalseForceLowestCeiling = FalseUnpauseOnReadyStatus = FalseForceTstormsWithCB = TrueAutoSetFSTime = TrueIgnoreFSLocationUntilReady = FalseAutoConvertPlanFiles = TrueAutoRefreshAI = TrueDisableVisGraduation = FalseForceRouteAloftTemp = TrueAutoSaveAETheme = TrueOfflinePlayback = FalseEnableVAS = TrueAutoGenVAS = TrueForceDestinationWeatherZone = TruePreventIcing = FalseOnlineUpdates = TrueExtendedDestinationWindsForce = FalseDisableAllGroundUpdates = FalseGlobalWrites = FalseDepictFS9HazeLayer = TrueExtendTstormLayers = TrueDisableDirectWindControl = FalseVoicePlayback = TrueLocalSuppression = TrueStartupSound = TrueDisableGroundUpdates = FalseUseProxyServer = FalseFogLayerGeneration = TrueUpdateSuppression = TrueOvercastEnhancement = TrueIgnoreFSReadyStatus = TrueFSUIPCWindSmoothing = FalseLimitSurfaceWinds = FalseLimitCloudLayers = FalseAutoGlobalWriteToggle = TrueRainWithTS = TrueDisableUpperLayerGeneration = FalseVisibilitySmoothing = TrueDisableMessages = FalseAutoTimeZoneDetection = TrueUpdateInterval = 10VATSIMData = TrueZuluConversion = 0AloftPredictability = 100WindDriftRate = 0MaxCloudThickness = 10000MinStratusSeparation = 7000TAFProcessing = FalseEnforceVisibilityLimits = TrueWakeTurb = TrueStartPaused = TrueUseSystemTime = TrueDisableCAVOKClouds = FalseProxyAddress = NONE

Hi,Sorry you are having trouble. Try these:Set VATSIM to FalseSet Supression Ceiling to 4000Please let us know.Hope this helps,JimActiveSky Sales and Supporthttp://www.hifisim.com/images/asv_dev_team.jpg http://www.hifisim.com/images/asv_proud_supporter.jpg

Hi JimI tried what you suggested but unfortunately, it did not work. Tonight I was on finals to EDDF 11nm and when I checked AS5, it was saying the closest airport was ETID 6nm. FYI I do run the route through AS5 before starting FS9. Any more suggestions?Gareth

Hi,This means that ETID was the closest station and was 6 miles away and you were 11 miles away from EDDF so that weather would not be fully functional yet. So this looks OK to me unless I am missing something!Hope this helps,JimActiveSky Sales and Supporthttp://www.hifisim.com/images/asv_dev_team.jpg http://www.hifisim.com/images/asv_proud_supporter.jpg

Hi,Well with "Force destination wx zone" enabled as such, and a flight plan correctly loaded, this would not be right, ETID should contain the same wx as EDDF. Although the aircraft is outside the 2nm exact wx zone for each station, the difference should not be that large.Gareth, can you please send us your .PLN from this flight along with the weather file (currentwxsnapshot.txt ought to do) to [email protected]? I will try to duplicate such behavior.. something isn't right.Best,

Gareth and DamianI would like to say that as far as the force Destination WX, option. It dosen't work for me either, and hasn't for Activesky for quite some time now, going back a few versions of the program. I have my suppression range at 100nm and force destination wx option checked and it has never locked onto the destination wx at 100nm or less, In fact it always changes to the destination wx on final approach at maybe 5nm or less from touchdown.If it worked as per the ASV manual, then when whatever the suppression range is set to and use suppresion range option checked and force destination wx option checked, it should lock onto the destination wx and suppress any updates when within the suppression range. correct me if I'm wrongthanksGary

Just pulled out the manual and checked on the Force destination WX option explanation and it says that if enabled then the Destination WX should be forced when within 80 nm of the destination and that has never ever worked for me even though I have the option enabled. It always waits till on final approach to update to the destination WX. Ny suppression ceiling is set to 4000, the range suppression is set to 80 nm and Use update suppression option is enabled, I always load a flight plan in Active Sky also.Gary

Hi,That is my fault. I did not notice that your were forcing your destination.Hope this helps,JimActiveSky Sales and Supporthttp://www.hifisim.com/images/asv_dev_team.jpg http://www.hifisim.com/images/asv_proud_supporter.jpg

Hi,After some additional testing we were unable to duplicate such failure in this feature. "It always waits till on final approach to update to the destination WX. "This does not really make sense with the way FS9 station-based weather works. The weather has already been set well ahead of your arrival. You are "flying into" the conditions and this will be visually depicted as such.What I think is happening is your visibility is dropping below the 9.99sm mark as you descend, causing a sky color change. This is a "known FS9 feature" that can be made better by using the new "Smooth Horizon" sky sets with ASVE's AE interface. Also, you could uncheck the "graduated visibility" option to prevent visibility from clearing as you ascend (and closing in as you descend). Using this with the "Depict fs9 haze layer" option will instead have the visibility shift at the top of the visibility layer ceiling instead of gradually as you climb/descend.Does this describe what is happening, or can you confirm there is indeed a failure in the force dest wx zone feature correctly cloning the wx conditions within 80nm of the destination?Best,

Hi Damian, Jim et al,Same problem is happening here. With all settings set to the correct values I always experience the 'force wx destination zone' not kicking in in those areas where wx reporting stations are situated in a relatively small radius from eachother. This is especially true in the KMIA, KMSP and KORD areas, and in some European areas, e.g. Frankfurt (EDDF), Amsterdam (EHAM), Berlin (EDDT), Madrid (LEMD).In the Closest Station Report window the final destination station is not being displayed till some 10-15 NM out of this final destination, in the case of my MIA approach only at 8 NM out KMIA wx was being displayed.Hope this helps in solving the problem.Hans

Hi Hans,Thnaks for that. Can you confirm that you are loading and processing a flightplan?Hope this helps,JimActiveSky Sales and Supporthttp://www.hifisim.com/images/asv_dev_team.jpg http://www.hifisim.com/images/asv_proud_supporter.jpg

Hi Hans,Cloest station report is just that, just a report... It has no bearing on the weather being rendered... Remember, ASVE sets the weather well ahead of your arrival.. it is up to FS9 to depict it for you accordingly. You "fly into" the weather that has already been set.Did you read my post about the visibility shift? I am almost positive this is what is happening, the shift is based on your altitude not distance. You can try other visibility options including unchecking visibility graduation.Best,

Hi Jim,Yes, I most certainly do. I also can add to my previous note that I solely do online (Vatsim) flights. The "Vatsim Online Weather" option therefore is activated as well. Do you want me to try to deactivate this option and see if all is working well then? If there is any other information I can provide you with, just holler and I'll be happy to send it to you.Hans

Hi Hans,No don't change that. Did you read Damian's responce to you? Could this be a visibility shift?Hope this helps,JimActiveSky Sales and Supporthttp://www.hifisim.com/images/asv_dev_team.jpg http://www.hifisim.com/images/asv_proud_supporter.jpg

Hi Damian,I'm not sure that this is caused by a visibility shift. You see, during the approach to the final destination, winds were different as being reported by the wx report (fetched through the Fetch a Report option in ASVE, that, by the way, reported the same wx as Vatsim's wx report for the destination area). I was well within the 80NM radius as enforced by the ASV Force Destination Wx Zone option. "Funny" thing is, that the winds I experienced were the same as reported for the station that was reported being the closest to me at that moment. (I checked this thru the Fetch a Report option as well). Weird, uh?I am not sure about any visibility shifts at that moment, to be honest, I didn't pay attention to it at the time.I will disable Visability Graduation and see what happens then. Will keep you posted.Thanks for shedding some light on the closest station report.Hans