I and others are finding that the time to respond to a handoff to departure or another control centre is too short if one is using a speech engine for ATC. What happens is that you receive the new frequency and respond with an acknowledgement. After dialing in the new frequency but before you can contact the new controller the previous controller comes on telling you to contact the next controller. Odd that it does so even though you are no longer on the previous controller's frequency. You are then rquired to acknowledge the handoff and the cycle can go on and on until you use the keyboard to break out. I realize that this behaviour probably cannot be fixed in the current version but would like to see the "nag time" limit afjustable for those of us who use speech engines to talk to ATC.

I and others are finding that the time to respond to a handoff to departure or another control centre is too short if one is using a speech engine for ATC. What happens is that you receive the new frequency and respond with an acknowledgement. After dialing in the new frequency but before you can contact the new controller the previous controller comes on telling you to contact the next controller. Odd that it does so even though you are no longer on the previous controller's frequency. You are then rquired to acknowledge the handoff and the cycle can go on and on until you use the keyboard to break out. I realize that this behaviour probably cannot be fixed in the current version but would like to see the "nag time" limit afjustable for those of us who use speech engines to talk to ATC.

if the copilot has the comms, and is instantly acking the changed, then the timer starts then. if you are running at 2x or 4x, you have to be 2x or 4x as fast dialing it in, and contacting the controller.jd

if the copilot has the comms, and is instantly acking the changed, then the timer starts then. if you are running at 2x or 4x, you have to be 2x or 4x as fast dialing it in, and contacting the controller.jd

The copilot does not have the comms and I am running in normal time. What I do not understand is why I am receiving anything from the previous controller when I have already changed the frequency to the new controller. The loop that I get into is particularly bad when I am trying to contact approach. Today I had to completely ignore the comms and finish my landing without talking to the approach controller. I think that as more people start using the speech engine for ATC this will become a more visible problem.

The copilot does not have the comms and I am running in normal time. What I do not understand is why I am receiving anything from the previous controller when I have already changed the frequency to the new controller. The loop that I get into is particularly bad when I am trying to contact approach. Today I had to completely ignore the comms and finish my landing without talking to the approach controller. I think that as more people start using the speech engine for ATC this will become a more visible problem.

make a log, send it to me, and let me see what's happening on your machinejd

Don't forget the only options are "Acknowledge" or "Acknowledge and Contact". Without acknowledging, RC will not know you've responded.If you change the frequency, you have contacted but not acknowledged... RC doesn't move on to the next controller until this acknowledgement is received.But, as for the time delays being far too short, I feel your pain.