Hi JD,so far, RC4 is astounding.Just a small question: is there a way to get the ATIS AFTER you get the Clearance during departure ? This is beacuse it happened to me, using Active Sky, that I got the ATIS about 5 minutes before the hour, then got my clearance, then got the taxi clearance, and while taxiing the new weather loaded and I wished I could re-check the ATIS (in fact, winds had shifted and visibility dropped from P6SM to 2SM) . I try to re-select the ATIS frequency but got nothing fo more than 3 minutes.Thanks a lot.

not at this time. sorry. we'll see if we can add that in a future versionjd

I set AS6 for a manual refresh. After the flight is loaded I switch to AS6 and I click the refresh button. I watch the status line and wait for the refresh complete message. If I do not see an AI refresh (as selected in my options) I activate that. This updates ATIS as well. Usually during prepping the parked aircraft (think fuel, initial NAV settings, etc.) the visual scene may change about a minute after after going back to FS.Only then do I start RC, load the flight plan, enter any controller or general options as well and then activate RC. All weather should now be in sync with AI following the correct pattern for the active runway. RC from active AI if present will detect the correct runway to use as well as deliver the correct ATIS.The delayed ATIS refresh and AI pattern updates are not unique to RC but FS ATC as well if you bother to bring up FS ATC just to get their ATIS.If you fly using real time weather instead of downloading current weather I believe you should check out the conditions available in AS6 for update suppression if any for take-off as they have for landing.Remember that RC gives priority to current AI patterns if AI is present.

JD: thanks if you'll make this availbale in future updates.Ron: I use too the manual refresh for ASV and start RC after ASV finished + manual AI refresh. I laso use offline archived wx.This time I was taxiing at KDEN just at about the "hour change" and in about 3 minutes the weather changed dramatically. I was prepared to this since the TAF was forecasting a wind shift and I already asked a different rwy from RC with respect to AI (thery were using 25 and I asked 35L). What I would like (and JD may put this in the next update) is just the availability of ATIS checking after initial contact.And JD: any chance to increase the arrival ATIS reception range for "leave frequqncy for wx" to more than 60 NM ? Sometimes things really happe fast during descent and some more time to correctly set up the approach would be appreciated.Thanks.

>JD: thanks if you'll make this availbale in future updates.>Ron: I use too the manual refresh for ASV and start RC after>ASV finished + manual AI refresh. I laso use offline archived>wx.This time I was taxiing at KDEN just at about the "hour>change" and in about 3 minutes the weather changed>dramatically. I was prepared to this since the TAF was>forecasting a wind shift and I already asked a different rwy>from RC with respect to AI (thery were using 25 and I asked>35L). What I would like (and JD may put this in the next>update) is just the availability of ATIS checking after>initial contact.>And JD: any chance to increase the arrival ATIS reception>range for "leave frequqncy for wx" to more than 60 NM ?>Sometimes things really happe fast during descent and some>more time to correctly set up the approach would be>appreciated.that seems like the appropriate distance. do you think atis can be received further out? >Thanks.

Well, I listened years ago in the cockpit ATIS as far as 100+ NM out, but maybe increasing the 60 now available to 80 could help in getting those couples of minutes more time to program the FMC/review the approach plates and so on. Or maybe letting you the listen to the ATIS without leaving the frequency (on box 2 for example): it takes about 1 or 2 minutes before hearing the ATIS when you get the "leave the freq for wx" approval, maybe setting the ATIS freq on box 2 beforehand, one could get the ATIS as soon as in the reception range (I don't know which is the ATIS reception range with standard MSFS ATC, it seems to be anything between 40 and 80 miles).Thanks again for your support.

JD,When I've been flying down at Pete Dowson's he says ATIS can be received once you're within 80 miles. That works for me too.Cheers,

How far out from destination do you look at the AI patterns?I am asking because twice when entering approach at LIRF and putting the data into the FMC for the anticipated runway, a few minutes later another "expect vectors to . . ." came up for the opposite 180 landing direction. In each case there was different destination weather for the flight.I'm just wondering if this was the case of possibly no AI present at the first runway selection statement and later AI showed up in the opposite direction, or, simiilarly, AI just changed direction during approach. This did not present a problem to follow this change and perhaps it might be more realistic anyway.

and that is one of the problems. i can only keep track of the closest 96 planes in the air. if you are 80 miles away, i won't see any planes landing or departing the arrival airport. so i will give you the runway based on ils, wind, runway length. once you are closer, i may see ai landing and departing, and we'll change the runway on you.60 seems reasonable to me for that reasonjd

This is a good reason: if you can't see the AI, you cant' guess what rwy they using. So I'll keep the 60 NM reception range and just hurry up with the FMC! In a future update could it be done to have a "VOLMET" feature ? Maybe one that could be personalized in the opening options, such as putting down the 3 or 4 ICAO codes of airports you need to be update on weather ? Or a more "real" one with real frequecnies and the real content of info ?The "leave frew for wx" enroute just gives you one station near your present position (and I can't remember if it says which one).Thanks a lot.