I know this topic has been discussed already, but I am not having any luck with a solution and reaching out for help.

As background, I am using fsx/radar contact and am using MCE to communicate to ATC myself.
I have no issue with clearance/ground/tower/ and departure. I also have no issues going over the Center the 1st time.

‘The Problems starts when Seattle  center directs me to go over to another Seattle center frequency.

‘I have acknowledged the change using several different methods (roger, and going over to 120.6 united 121, and many other voice commands).

in the text to speech window, I can see that my commands are being heard correctly, so I then Change to the new center’s frequency and with United 121 with you at 13 thousand ( which is also acknowledged). Then comes the nagging… the previous center keeps telling me to change frequencies to the new controller.

‘This happens over and over even though I should not even hear him since I have already changed frequencies.

 

I read in the threads to try two things;

1. Just say “Rodger” to center and quickly switch frequencies to the new center and announce “United, 121 with you at 13 thousand.”

 The thought is that the switch to the new center needs to take place very fast, but no matter how fast I do this It does not stop center from following me over to the new center and spamming me with repeated warnings.

2. Ignore the spamming and contact the new center on the new frequency and the previous center will stop nagging.

This also has not worked for me.

I do not have any issues when I have the FO run the radios/atc, but I prefer the added level of realism communicating myself.

Does anybody have any suggestions?

below is a previous post on the subject;

 

“I've just completed several flights using MCE push to talk with RC4. I used David's idea of simply saying 'Roger' then telling the FO 'over to center' and it worked very well.

I've also used the FS++ option to let MCE acknowledge the 'nag' command and simply move on. It also works.

Not sure which method I prefer, let the FO take complete control of comms, use the shortened version of 'Roger' (not as realistic), or the F++ MCE 'acknowledge' the 'nag'.”

 

Edited October 7, 20214 yr by Polmer
Mis spelled word

11 hours ago, Polmer said:

I know this topic has been discussed already, but I am not having any luck with a solution and reaching out for help.

As background, I am using fsx/radar contact and am using MCE to communicate to ATC myself.
I have no issue with clearance/ground/tower/ and departure. I also have no issues going over the Center the 1st time.

‘The Problems starts when Seattle  center directs me to go over to another Seattle center frequency.

‘I have acknowledged the change using several different methods (roger, and going over to 120.6 united 121, and many other voice commands).

in the text to speech window, I can see that my commands are being heard correctly, so I then Change to the new center’s frequency and with United 121 with you at 13 thousand ( which is also acknowledged). Then comes the nagging… the previous center keeps telling me to change frequencies to the new controller.

‘This happens over and over even though I should not even hear him since I have already changed frequencies.

 

I read in the threads to try two things;

1. Just say “Rodger” to center and quickly switch frequencies to the new center and announce “United, 121 with you at 13 thousand.”

 The thought is that the switch to the new center needs to take place very fast, but no matter how fast I do this It does not stop center from following me over to the new center and spamming me with repeated warnings.

2. Ignore the spamming and contact the new center on the new frequency and the previous center will stop nagging.

This also has not worked for me.

I do not have any issues when I have the FO run the radios/atc, but I prefer the added level of realism communicating myself.

Does anybody have any suggestions?

below is a previous post on the subject;

 

“I've just completed several flights using MCE push to talk with RC4. I used David's idea of simply saying 'Roger' then telling the FO 'over to center' and it worked very well.

I've also used the FS++ option to let MCE acknowledge the 'nag' command and simply move on. It also works.

Not sure which method I prefer, let the FO take complete control of comms, use the shortened version of 'Roger' (not as realistic), or the F++ MCE 'acknowledge' the 'nag'.”

 

I'm afraid it's a limitation of RC4.

Can't blame it because it was intended for keyboard interaction, with most people choosing the auto-tune option.

Even without MCE at all, some users find the time to switch to next controller is far too short when you have to dial manually. And I agree, normally as soon as you move from previous freq, controller shouldn't nag you.

Pretty sure the RC4 guys would have addessed the issue if it was still an ongoing project. And it's freeware now.

Best advice I can give is to shorten acknowledgments (especially with intitial clearance), then instruct Fo to dial next freq as soon as you are instructed to do so, with "gound to ground", "switching to tower".

There is a trick you can use when controller or traffic is transmitting in the mniddle of you own transmission, which is to carry on with your message, but only release PTT when nobody else is transmitting. You can hold PTT down for up to 30 seconds. After that, message will go through anyway

See this awesome video, courtesy of David. Radar Contact ATC integration included

<media> 

</media>