Hi to all. I am fairly new to flight simming and I have a question.I have RC4.3 installed and it seems to be working just fine with my set up the only issue at this time is that atc seem to be a little anxious for my replies to change controllers.I have Multicrew installed and it seems to work fine but when i get a request to go to any other controller either centre or airport tower or whatever.I reply and with in 2 to 3 seconds before I can set the frequency it asks me again. I am not sure if it is a problem with RC4.3 or Multicrew can anyone point me in the right directionthanks for the help in advance.Flying Big D

RC has an option on the General tab that will tune your COM1 automatically called Autotune on Contact. RC also uses its own frequency database and expects you to tune that either manually or by setting the Tune on Contact option. The command "Ack and Contact" uses this as well or when you initiate issue communication requests such as getting clearances, requesting taxi, etc.I am not familiar with Multicrew Experience but if any of its functions try to tune COM1 that could be a conflict. It might be OK if it tunes the same frequency but likely if it has its own comm database of frequencies it will not match RC's fixed database (not pulled from your installed scenery).RC4 also has a copilot feature that will conduct speech and tune COM1 as well activated by a hot key toggle to switch COM1 control between copilot and pilot (you) that can perform a copilot's communication procedures. If Multicrew Experience also is allowed to perform this action using its own COM frequency database that can be a conflict. If the copilot has comms he/she will automatically respond to ack and contact an ATC command.

Hi,MCE can use rc.You must check that option, otherwise it will use the default 1What i do if i must change freq is 1st dial the new freq, then ack, change it and then contact`.Sometimes if mce doesn't understand it, then you'll have the button option.:( John

Hi to all. I am fairly new to flight simming and I have a question.I have RC4.3 installed and it seems to be working just fine with my set up the only issue at this time is that atc seem to be a little anxious for my replies to change controllers.I have Multicrew installed and it seems to work fine but when i get a request to go to any other controller either centre or airport tower or whatever.I reply and with in 2 to 3 seconds before I can set the frequency it asks me again. I am not sure if it is a problem with RC4.3 or Multicrew can anyone point me in the right directionthanks for the help in advance.Flying Big D

Hi,MCE Co-pilot will not automatically tune the frequency. You need to ask him/her to tune the new frequency each time a switchover is required. Therefore, zero chance of any conflict.You may want to read the following RC4 threads.http://forum.avsim.n..._1#entry1902669http://forum.avsim.n..._1#entry1812914Cheers,Geraldhttp://www.multicrewxp.com

Hi Flying Big D,this is a well known issue with RC4 as the threads speedbird 105 mentions show.MCE doesn't support the "Autotune on Contact" function of RC4, also it doesn't allow you to hand the comms to Otto.So you have to(1) ack the handoff(2) tune the new frequency(3) contact the controllereach time a switchover is required.RC4 gives you very little time to complete this process before they "remind" you (possibly on the freq you have already left!).Maybe I'm slow but with MCE I hardly ever managed to do this on the first try.(I'm using FSX/RC4 in a server/client configuration. That might have aggravated the issue.)For me It's Your Plane works much better although its approach is more "primitive".If you get a good reaction speed with MCE on your system and don't mind handling the comms all of the time it's certainly a good companion to RC.By the way: the two threads mentioned are almost 10 months old and in there Pete Dowson suggested an interim version of RC (RC4.4?) to address this problem.Has this been considered?agutz

To delay RC4 'nagging' don't ack a command until you have complied. This gives time to initiate the aircraft performance change.The second type of 'nagging' is not responding to communications soon enough with an ack but this is longer than the time RC waits for an aircraft performance change. There is an inherent caution to be observed when delaying an ack, however. If you cross a waypoint in your plan that RC would credit while not acknowledging (acking) an atc command, RC will not observe you crossing that waypoint for credit and will vector you back to it. If you do need to skip a waypoint you can go to the extended menu (9), the choose direct-to, then from the list pick your next waypoint to aim to. When you do this RC will expect you to fly direct from your present position to the waypoint you chose.