I just recently purchased RC. When I first started running it, I found I was missing the msstdfmt.dll and it wasn't in my windows\wow64 directory. I had to download it from the internet and then I was able to install as the Pinned topic suggested.I was then able to rebuild the databases and then finally run RC from within FSX. The problem I'm seeing now is that RC takes forever to see a keypress once I start and I'm sitting at the airport. I see the RC display on my screen and I try to get ATIS by hitting the key and it sometimes takes like 10 or 20 sec to respond. Sometimes not at all. I'm not sure what the heck is going on here :(I'm running FSX on a Intel Core 2 E8500, with 4 gig memory on Windows 7 64-bit Pro.Any hints as to what's going on. I'd really like to try this after spending $50

I also notice that when it does finally see a keypress it will show "Standby" on the screen.....several seconds go by and then it will go on to the next screen.Sometimes it will perform 2 or 3 key presses in a row after a long delay between.

the interesting thing about this is this is a fresh install of win7 64bit pro and that file did not exist in the windows\wow64 directory. I wonder if their is a 64bit version of this that I have to download from somewhere and I installed the 32 bit version? Why wouldn't MSSTDFMT.DLL exist in the first place?

To improve performance, turn off prerecorded chatter and use only AI chatter. In addition run with Display.txt disabled.Get the current fsuipc from the links in the forum above, in fact insure makerwys.exe is current as well (in the sites FS2004 section but for FSX as well).Your RC version should be 4.3.0.3843 or 4.3.0.3845. If not post here and you will be instructed how to download this last version (without charge from jdtllc). There were some changes in audio handling that affects RC's response time to menu changes.With the current FSUIPC indicated, you should in your modules folder rename advdisplay.dll. It is no longer used (unless another app might need it but doubtful) with the RC in flight window providing a response area.Remember that for the most part FSX and RC and most other add-ons run on only one core of your processor and even graphics are rendered by that CPU. You should have audio off of a separate card rather than your motherboard to improve performance overall.What other apps are running along with RC?Independent of RC many FSX users can't run at full scenery sliders on that processor and of course if FSX is "slow" RC will be as well.These are general but check into this stuff.

To improve performance, turn off prerecorded chatter and use only AI chatter. In addition run with Display.txt disabled.Get the current fsuipc from the links in the forum above, in fact insure makerwys.exe is current as well (in the sites FS2004 section but for FSX as well).Your RC version should be 4.3.0.3843 or 4.3.0.3845. If not post here and you will be instructed how to download this last version (without charge from jdtllc). There were some changes in audio handling that affects RC's response time to menu changes.With the current FSUIPC indicated, you should in your modules folder rename advdisplay.dll. It is no longer used (unless another app might need it but doubtful) with the RC in flight window providing a response area.Remember that for the most part FSX and RC and most other add-ons run on only one core of your processor and even graphics are rendered by that CPU. You should have audio off of a separate card rather than your motherboard to improve performance overall.What other apps are running along with RC?Independent of RC many FSX users can't run at full scenery sliders on that processor and of course if FSX is "slow" RC will be as well.These are general but check into this stuff.

Well, its working normally now. I uninstalled, then reinstalled and re-registered and it's running good now. I dunno what's up with that, but thanks anyway. :)

Hello I had that problem as well turns out i did'nt have the clock running on the flightdeck.Anyway glad you got it sorted :( :(