Sorry I'm not sure if there is a bug here. I suppose I'd just like to know if what I'm experiencing is the norm. I'd just say I didn't use the previous beta, but decided to 'take the risk' with the new one.When I start AS, there is quite a long period of writing to FSUIPC and FS. When the update is complete, I open a flight plan. I can't yet press the Process button because a further bout of FSUIPC and FS updating takes place. When that is complete, I can process the flight plan. That complete I get the wxReport but that appears to hang. Atleast the Close button has no immediate effect and neither has the up/down arrows. Eventually, the wxReport disappears, but it isn't clear if the f/plan has been properly integrated.Maybe something a touch awry here?Bud

Bud,You're not the only one experiencing those things with the public MR1 betas (Build 81 and up). Writing to FSUIPC does take longer, since Damian is writing the weather to more stations and of course, AS2004 immediately does an initial write, provided you already started FS9 and have loaded an empty flight and plane.Also, I get the same effect when loading a flight plan that you describe. I can't enter an alternate for quite some time, since AS2004 immediately starts writing to FSUIPC again. Whether that's intetional or not I can't say, but it happens to me on every flight plan import.The hang after processing the flight plan is somethign I encounter occasionally, but I am assuming that if the Nac Log ends up bein accessible and correct, the plan was properly processed.Just my $0.02, I'm sure Jim or Damian can shed more light on this ;-)By the way, those delays don't bother me all that much, now that I know that they exist.Best RegardsMax (Bern, LSZB)http://www.hifisim.com/images/as2004betateam.jpg http://www.precisionmanuals.com/images/forum/800driver.jpg

Hi All,Yes, a long write to FSUIPC is normal and as long as you can view the nav log your plan was processed.Hope this helps,JimActiveSky Support

Hello JimMany thanks. Good to know the time delay is not a prob. The one thing which is still not clear is that I cannot properly review the nav log. As I mentioned, the up/down buttons do not seem to be operable. Could it be that the buttons are not operable because the report form is not, how shall I say, stabilised. Maybe I should give it a little time once it appears on the screen before I poke about with it.Bud

Hello MaxThanks for the reply - it's actually quite comforting to know that I'm not alone. I agree with you, the delays don't really bother me that much now I know it's not a prob.Best wishesBud

Bud,Are the up/down arrows grayed out or not just working? Grayed out means that there is nothing to move up or down. Not working means that another process is taking place; either a download of data or a write to FSUIPC.Hope this helps,JimActiveSky Support

Hello JimNo they're not greyed out - clearly something else is happening. I need to be more patient before I start fiddling I reckon.I've actually tried out a couple of flights and I have to say the weather environment was excellent. I'm a long time user of AS and it is so good to see that things are getting back to 'normal' as it were. Just one odd thing to report re. baro settings. I've got the baro set appropriately, but the default ATC keeps insisting that my flt level is wrong. For eg I've descended to 7000 as instructed with baro at standard in Europe. At that level ATC keeps asking me to expedite my descent to 7000. Same thing happened a couple of times during the climb phase - I'm using PMDG 737NG. Bud

Bud,Welcome to the world of the VERY functionally challenged FS ATC. For FS9 ATC, the transition altitude is ALWAYS 18000 no matter where you fly, which is why it yells at you to expedite your climb / descent ;-) You will always need to set actual pressure when flying below 18000, if you're using the FS ATC, so much for "as real as it gets" *eg*Best RegardsMax (Bern, LSZB)http://www.hifisim.com/images/as2004betateam.jpg http://www.precisionmanuals.com/images/forum/800driver.jpg

...>out means that there is nothing to move up or down. Not>working means that another process is taking place; either a>download of data or a write to FSUIPC....Would it not be better if the cursor changed to an hour glass, as per standard windows UI, in this case?Steve

Thanks Max - y'know I never knew that. I usually use Radar Contact and have not had this before. This is my first venture into the world of the default ATC and have to say there are some good things in it - transition altitude being not one of them!Best wishesBud

Hi Steve,Not sure, and a good idea, but the main window does display the status messages.Hope this helps,JimActiveSky Support

>Not sure, and a good idea, but the main window does display>the status messages.Jim,Why don't you think it is a good idea? It is standard GUI stuff.Steve

Hi Steve,Re-read my message to you!"Not sure" meant that I WAS not sure if it would be better. I'm not the boss!"and a good idea" meant that it IS a good idea! Thanks for the suggestion!The rest is just pointing out what is available right now!I know I wasn't too clear now. Lots of "junk" was happening at the same time and my mind wasn't working properly. Keep those ideas rolling in!Hope this helps,JimActiveSky Support

Jim,My apologies, it does help to read all of the text :-) In my (weak) defence, I read the "not sure", and it threw me.I will read _all_ of the mesage next time!!!Steve