Lock again?

Howdy guys,I'm not getting over this way much anymore due to the tremendous slowdown in the forum loading hosted by AVSIM now. It just takes too long for me to load up anymore. However, I have been keeping abreast of the updates and new builds for AS. Thanks once again for your continued good support. The reason for this post, is to confirm what many others are seeing still (build 84), to do with pop-up clouds, sudden transitions, etc., and perhaps offer a possible idea to look at in the way of a partial solution. I am wondering if there might be any connection between some of these issues and coastal areas, since that is where I do a lot of my flying, and where I notice the greatest number of problems. Now, for example, on a flight today from Goose Bay (CYYR) to St. John's (CYYT), Goose was reporting only scattered clouds at 24,000, which I had. No problems there. The route took me out over the Straits of Belle Isle between the southern coast of Labrador (Canada) and the northern coast of the island of Newfoundland. As soon as I got over the coast, the clouds popped from view and I had totally clear conditions until reaching St. Anthony, about 50 miles south of the northern coast. The only other anomaly was 3 very rapid pressure changes on climb out (all within about 10 seconds), but they weren't really terrible and frankly, not worth worrying about. Winds never gave me a problem, incidentally. The smoothing seemed to be really good. The main problem started on descent into St. John's. I passed over the Gander VOR (YQX) and turned eastbound and headed more or less out to sea. Once I hit the coast, the undercast (by the by, the Flightwatch was giving me 32012KTS 8SM Moderate Snow OVC026 OVC046 -4/-7 29.63 for YYT, and Gander's weather was actually worse) suddenly disappeared off in the distance. I could see clouds to the south and north, but none in front of me, right to the horizon. As I got within 10 miles of the airport on the approach to 29, I was quite suddenly enveloped in clouds again, and except for the fact it wasn't snowing, I was now in the wx that was being reported. It wasn't until I was in at the gate that the snow itself actually started showing up.OK, you've heard all this before from others, so we know it to be an issue (still) and I'm quite certain that Damian and crew are fighting as hard as they can to overcome this stuff, despite MS' best efforts to make that job all but impossible. I get the feeling that we are fighting an uphill battle here. With that in mind, I'm wondering if one solution might be to revisit the "destination lock" idea again. I know this has been raised a few times in the past, and so far the reasons for not doing it have been quite valid (obviously - we aren't dealing with a bunch of stubborn people who just want to do it their way here :-) ). But, I still believe that this might be a valid solution to a big problem. The most important weather we can have is at departure and destination. So far, departure seems to be reasonably ok. However, for some reason, destination stations seem to have widely differing reports from the nearby "satellite" stations, and this seems to be causing no end of grief when it comes to programming. I know there is a function that in sparsely settled areas, you can force the weather to your destination, but that's not terribly realistic. What I would propose would be that your destination station (which has to be inputted to the AS program, as in a flight plan or similar arrangement), have a force option whereby once you get inside the preassigned radius of that station (say 30 miles, but make it user-adjustable), all nearby stations are ignored in favour of the destination wx. Yes, if you divert from Sibling Corners International to Puddle-Jump International that is only 10 miles away from Sibling, you aren't perhaps going to have exactly the correct weather there, but it will be close. I've seen many instances in FS were one airport is reporting overcast conditions, where the nearby one is reporting broken or less. Why this is happening I'm not sure, but it seems to be at the crux of the problem here. I think if we can get past this bit, then the rest will either fall into place, or we'll simply have to live with what we have (Damian has already accomplished his allotment of miracles for FS9, I would think :-) ). The upper winds are MUCH better than ever before, pressure bumps are all but gone (and it seems the ones that may remain aren't really a problem), and we have much better cloud enhancements in FS9 than the default (like enhanced overcasts).Anyway, I do apologise for the rather long post, but I thought I'd make the most of my time while here :-). It might be something to think about guys. Remember, the lock and radius would be defined by the user, and the user would have to accept that his nearby field may not be totally accurate if he diverts and the new destination is within the radius of his locked field.Thanks for the ear. GlennPS - have a default setup of FSUIPC and AS2004 Build 84