Hello again, I was able to change the delay time between WAV files from 750-800 milliseconds, staccato form, to what I consider normal speech delays by minimizing FS2002 as soon as I clicked on Clearance. If I choose Clearance with FS2002 at full-screen I get the above mentioned delay. Wow!! My problem with the delay in sound might be caused by my own settings for FS2002 or the GeForce4 card I have, or both, and has nothing to do with RCV3 itself although it isn't apparent with RCV2.2. So let's dig into those settings right here at home. Hmmmmm.Cheers

Blais,Yes, we are well aware that minimizing 2K2 helps a lot. It speeds up anything external to FS. Problem is, though, it's really difficult to fly that way. ;-)Your FS settings are probably fine. We'll find a solution somehow without flying blind.Thanks for your info.

I've tried changing my video settings, and sound acelleration. The only thing that seems to help is running RC on my networked laptop. Works great, and fs runs faster too.I dont think theres anything more I can do to troubleshoot. I've done everything I could think of. If you want something checked, let me know. On a side note, I've installed the 41.09 detonators, and they seem to work great. I sitll can't run FS in 16x12x32 tho.

Scott,Thanks for this tip! My "slow" voices weren't too bad, but after checking my DirectSound settings, I found that the debug slider was set halfway. It's now set off and my controller and pilot voices are back at v2.2 speed and quality. Definitely worth trying this "fix".Lindsay.Win98SEAMD 1900+ XP512 Meg PC2100Onboard sound (AC97)GeForce 3 TI 500Full install of RCv3

Lindsay,Excellent. It's been so long since I fiddled with DirectX I had completely forgotten that problem. Thank goodness it was right there in the FS forum.I myself just tonight reset the DiectSound setting to DirectSound from Primary Sound Driver. So it pays to check those DX settings!

Hi Scott, I am sure you guys will. I tried reducing all attributes and FR on my video card, etc, etc, and, as you said, the only thing that seems to help is minimizing FS2002. Yup, hard to fly that way. No big deal though. I just re-installed v2.2 and will use that for my counterfeiting of my granddaughter's flight from Germany but have V3 on this machine and will wait patiently. Don't bust your behinds on the issue. It will be here tomorrow.Take CareCheers

Well, lots of observations through lots of trials. Lots of conclusions based upon a "computer illiterate" brain that I possess. My apologies in advance if I rattle on for awhile.System:P4 2.2 gigSoundblaster Audigy Platinum Sound CardVisiontek GF4 Ti 4600DirectX 9 BetaWindows XP Professional with service pack 1 installedOK. Downloaded latest sound card drivers from Creative. No change in RC3 performance. Downloaded 4109 video driver from Nvidia. No change. Defragged hardrive. No change. With Windows XP you can hit ctrl/alt/delete and bring up Task Manager. Since I use four monitors I pulled Task Manager where I could see what was going on while using FS2002 and RC3. My CPU was running at 100%. I sat with FS2002 cranked up while in the default Cessna 172 at KASG airport looking South. The ATIS was very slow as it had been before. I noticed the "mountains" of the Ozarks (really hills) and remembered I had one of those terrain CD programs installed. Shut down and took the terrain programs out. Went back to same situation and I noticed I was making immediate progress with CPU useage being less. So much so that the ATIS was playing quite OK. Then, I started playing around with lots of video selections. I turned off all video options. Frame rates went through the roof at around 150 or so. Radar Contact was chiping out the ATIS just fine and I was noticing it hardly used any CPU resources at all-from 2 to 5 percent and that only occured when a wave file needed to be brought up it looked like. Radar Contact ran just fine. I shut down two of my four monitors. That brought CPU useage down also but not much even though there was nothing being put on the other monitors except Task Manager. I one by one brought back up the video selections to maximum and checked the results with Task Manager. I also selected weather programs and different airplanes and different cockpit views. Summary:1. It seems you must have overall CPU useage less than 100% for Radar Contact to run smoothly. Something under about 95% on down or so seems best.2. Radar contact uses hardly any system CPU resources at all. Only a couple of percent and that is not very often.3. FS2002 is a CPU hog and will skyrocket to 100% if you select any sort of difficult scenery backgrounds while on the ground. This makes ATIS in RC3 sound choppy and slow. 4. Selecting the virtual cockpit sends the CPU to 100% immediately and it stays there. 5. Turning off the 2d Cessna panel uses more, not less CPU resources. A big suprise to me. Using the IFR panel really brings down system CPU useage.6. Tried several other Payware airplanes and they all sent CPU useage to 100% immediately whether in 2d or Virtual cockpits. 7. Tried the default 737 and it sent the CPU to 100% also. Only the default Cessna worked although I did not try all the other default airplanes. 8. Once airborne on a flight plan from Springdale (KASG) to Olathe, Kansas, at 6,000' I started selecting all the video options one by one back on again and the CPU stayed well below 100% and Radar Contact ran beautifully the whole way. If you come back down the useage will go back up and Radar Contact once again slows down. 9. Using terrain mesh programs will stick my CPU to 100% whether or not I have the Terrain Mesh Complexity slider full off or not. Only removing the program got the CPU useage down. 10. Using online weather programs sends my CPU immediately to 100% and it stays there no matter what else I do. Radar Contact suffers appropriately. Using weather selected within FS2002 (not online weather) works just fine with minimal CPU impact. I only tried broken clouds in my face.11. Using Adventure Display sent CPU right up to 100%. Docked or not. Any sort of additional message display window wreaked havoc on the program unless I stuck it on a second monitor. Interestingly, the default GPS window did not cause much of a problem whether on the main screen or on a second monitor. Conclusions:1. There is nothing wrong with Radar Contact. It is an outstanding program. It hardly drains any resources at all.2. A solution needs to be found to enable FS2002 to share resources with Radar Contact if that is possible, or to enable Soundblaster Audigy Platinum (and others I'm sure) sound cards to butt in and play these wave files when FS2002 has maxxed your computer out to 100% and that is about all the time if you are doing anything. 3. I am certain that you computer wizards out there will have this problem fixed in no time. I sincerely hope this is of some help,Bob, Rogers, Arkansas

did you check the directx debug level, that scott mentioned in one of his posts?

Surely he won't have that option if he's using XP?AndyEGTR

I downloaded the file talked about and stuck it into Windows System 32 folder. Clicking on that out of Control Panel gets you the options of working with DirectX. The slider was all the way to the left.Bob, Rogers, Arkansas