I saw something posted on this a while back, but I've searched for about 1 1/2 hrs and can't find it. Hoping someone will be patient enough to answer this again.I like the fact that RC3 can disable the Pilot portion, so like real ATC you speak back. I'd like to still acknowledge the transmission through a keystroke but without pilot voice.When I clear the checked options for 'play pilot wavs' and 'pilot autoreply', it appears that RC3 does not allow me to ack. Also, it often plays chatter immediately after the transmission where I would normally reply.Am I doing something wrong? Is there a workaround for this?thx.Kevin

if you don't want to hear the pilot's wavs, uncheck play pilot's wavs.if you have pilot autoreply checked, there is nothing to ack, it is done automatically.so you would want to uncheck play pilot's wavs, and uncheck pilot auto reply

* I've done this (unchecked both boxes), however the acknowldgement happens automatically, the controller does not wait for an acknowledgement. For example, after calling Clearance Delivery, the controller immediately says readback correct. The 7 key for acknowledge doesn't seem to do anything. Also, my repeat instruction doesn't work either. Haven't tried reassigning the keys yet...will do that.* Another problem, when the pilot wavs are off...traffic calls (without course change) are followed by pilot ack wav.* Also, chatter wavs sometimes play immediately after the controller issues an instruction. So if you want to do a verbal ack, you get blown over by the chatter.* Got it running on the networked PC with a headset plugged into it so all of my ATC comes through the headset. AWESOME. Really enhances the experience.>if you don't want to hear the pilot's wavs, uncheck play >pilot's wavs. >>if you have pilot autoreply checked, there is nothing to >ack, it is done automatically. >>so you would want to uncheck play pilot's wavs, and uncheck >pilot auto reply

>* Got it running on the networked PC with a headset plugged >into it so all of my ATC comes through the headset. >AWESOME. Really enhances the experience. But what about all the other sounds, then?

Rename the pilot wav folder which I think is "1".This stops the response wavs and allows you to acknowledge.I've done this to allow me to use Game Commander to acknowledge the commands with voice.

Great,Thanks, I'll try that.>Rename the pilot wav folder which I think is "1". >This stops the response wavs and allows you to acknowledge. >>I've done this to allow me to use Game Commander to >acknowledge the commands with voice.

Since RC is running on the second PC, only the ATC goes through the headset (plugged into the sound card of the second PC). All other sound is generated as usual on the 1st PC running MSFS.>>* Got it running on the networked PC with a headset plugged >>into it so all of my ATC comes through the headset. >>AWESOME. Really enhances the experience. >>But what about all the other sounds, then?

>I like the fact that RC3 can disable the Pilot portion, so>like real ATC you speak back. I'd like to still acknowledge>the transmission through a keystroke but without pilot voice.>>When I clear the checked options for 'play pilot wavs' and>'pilot autoreply', it appears that RC3 does not allow me to>ack. Also, it often plays chatter immediately after the>transmission where I would normally reply.>JD,I have the identical issue as well. It seems that even though "Pilot Auto-Reply" is unchecked all transmissions are acknowledged anyway (albeit "silently" if Play Pilot Wavs are uncheck). The only work-around seems to be renaming the "rcv30winwood1" folder to something like "1.bak" in order to be able to manually acknowledge transmissions. Perhaps you can revisit this in the upcoming 3.1 update. Thanks again for a wonderful program and outstanding support.Regards,Nick Anzelino