Hi Jim,OK, I'll stay away from the Vatsim Online Weather settings. Read Damian's note and replied to it. As far as I can see it wasn't a visibility shift, but I'm not 100% sure about that. I'll pay more attention to this during my next flight(s) and will keep you updated.Hans

Hi Damian/Jim,I've got some more information for you. I just finished a flight into Paris' LFPG. http://forums.avsim.net/user_files/133298.jpgThe included picture shows that I was 34NM out of LFPG. At the time I made this screenshot I was flying at FL060. My ND showed winds 337@15,almost the same winds as shown for LFAF in the above picture and a 12 degrees discrepancy with the winds shown for my destination LFPG. The weather reported for LFPG in ASVE was the same as reported for LFPG by Vatsim. Am I right in thinking that the experienced winds should rather be 325 (give or take 2-3 degrees) than the ones blowing out of 337 I experienced at FL060?Hans

Hi Hans,This unfortunately only tells part of the picture... The "Fetch report" shows METAR data directly from the WX file for closest relevent ICAO wx station. This is always a direct pull from the data file each time the fetch button is pressed.The closest station report shows the closest actual FS9 wx station with the in-use metar/taf/aloft data. This data can be suppressed (using last data set instead of current to prevent visual shift) depending on options, which would (by design) show a discrepency between closest and fetch reports. The actual wx written to FS9 can also be different, depending on options. If force dest wx zone is enabled, for example, all wx structure data is cloned for all stations within 80nm of dest (and closest station report is fairly meaningless). In your screenshot, LFAF is the closest FS9 wx station, and the data that "would have been" in use is shown by the METAR string but as mentioned since this is within 80nm of dest, it is actually be cloned from LGFP. We don't know what LGFP's METAR in use is from any of this data (fetch is showing file data, not METAR in use).It would be better if we forced the closest station display to show the destination METAR instead of actual current closest station (when dest force enabled). We'll put this one on the list....As for the force dest wx feature, I can confirm that this is working properly in all test scenarios I've tried and as supplied by users. The only time a discrep between dest and 80nm-vicinity ID's will occur is occasionally due to cloud heights/large terrain differences in which the cloud heights might slightly vary. Cloud "types" (stratus,cirrus,cumulus) can also vary between these stations by design for more realistic visual representation. Actual conditions should always be very consistent within the 80nm zone. In conclusion, at this time we cannot verify any problem in the force dest wx zone feature but will continue to check it out in detail (please keep detailed reports and logs coming). We'll also work on improving the way reports are shown (i.e. lock display to dest within 80nm) to make things more logical and intuitive.Thanks for the feedback!

Hi Damian,Thanks very much for your comprehensive explanation. It dawns to me that indeed I may have been mislead by the data being displayed in the 'fetch report' and 'closest station' reports. :)Thanks,Hans