I'm trying to get a handle on the reasoning for the destination wx lock distance being so far out. I was going to recommend that it be dropped from 80 down to something much smaller in ASE, and I see now it's 128 in AS2012 according to the manual. What I'm finding is that I can do a 100 nm flight and get the identical wx for the entire flight, unless I disable the option then re-enable it when I get closer. My thinking is that within about 30 nm you are going to see very similar wx, but at 128 nm you can have a really wide range of conditions. I'd be interested to know what the reason(s) is/are for having so great a lock distance. I'm not being critical here as I've learned that things are usually done for a good reason, but in this case I don't know what that is :( .Many thanks (still loving the program and it's working great for me!)

Hi Glenn,It was upped to 128nm due to requests from many users and also our beta team, primarily in effort to better force proper AI handling without unexpected runway assignments. Yes we understand the issue with short flights not having variable weather when using this feature, but the consensus is those flights probably shouldn't be using the feature. With that said I can see how having a smaller range here would be helpful for some users/flight scenarios. Making the threshold range configurable is something we can do, if there is interest?

Hey Damian,Sorry, would've answered yesterday but I was away.Thanks very much for the answer to this. I'd be all in favour of having a user-adjustable distance option. Now it would appear as though it's not a major preference for others so I wouldn't expect you to do that for one customer. I understand now the "why's and wherefores" so that's fine - majority rules :( . If it's something you can do in a future upgrade without knocking yourselves dead on it, that would be great. Otherwise I simply do the manual option that I'm using now.Thanks again. Back to the "friendly skies" :(