I am using Multi Crew Experience to control RC4 by voice. The combination works really well, recognizing my voice & choice of phrasing just about every time & I must say I cannot imagine 'flying' without either of these programs now.

I just have one recurring (minor) problem - Whenever I am told to change centre, and am given a new frequency, I acknowledge the instruction, but while I am still dialling the frequency, the original controller calls me again and tells me to please contact the new centre.

I like to change the frequency and make the calls myself rather than just hit 'ack & contact'. Is there any way to increase the time given to adjust the radio? If I was being slow then I could understand it, but I am being as fast as the mouse will click! It is like a race against the clock trying to change the channel and get the call in. (I don't mind the fact that the original controller is still able to call me even though I have moved away from that frequency   ).

 

I can change some of the controls on my button box and get a couple of rotary encoders working, which will hopefully allow me to switch more quickly, but I would really like to slow this down if anyone has any ideas/advice.

OK, I now see that the 'tune on contact' option allows me to contact the next center without dialling the numbers. I will have to use that option, but I'd be interested to know if it is possible to set them myself without the controller always asking me a second time to change frequency.

If you are not near flying over a waypoint to be credited try dialing the frequency before acking ATC. You may then get a repeat command though from the impatient controller. 

 

If you are flying at 2X this would be more of a problem.

Ah, I am flying normal speed, but I am only flying direct at the moment, so I still have a lot to learn about waypoints, I still do not understand about choosing or using them, so thank you again, I am still reading through the manual & will study them now. But also since realising how 'tune on contact' was operating, the issue has reduced massively, & I am steadily improving my own efficiency as well.

 

I must say, for anyone wondering if this is worth buying - yes I am having a challenge setting everything up to work smoothly, but that criticism is not directed at RC4, it is a result of the total of all my fsx addons, and the combination of control devices. And despite the challenge this is presenting, I cannot recommend it highly enough - it completely transforms the immersion and experience of flying & takes it to another level. This is also true of Multi Crew Experience, and both together are fantastic.

 

So I still have a major overhaul of my controls needed - my plane is not really fully airworthy at the moment. My cockpit is adapted from my motor race sim gear, so I have my Logitech G27 wheel & pedals, a DIY button box, a 'pro-race' dash, and a Logitech extreme 3d joystick - over 70 buttons on 4 devices (plus mouse), and it is working really well except for the fact that there will occasionally (too often at present) be an unexpected action at unfortunate moments due to the control conflicts.

Last night I was 1 mile out from touchdown at KSFO when I apparently requested a switch to Reno! And the night before, I allegedly asked if I could return to Las Vegas, while I was just turning onto final approach at KLAX. I have also had missed approach declared twice for no reason. Oh, and  'I' am always asking to leave the frequency for weather.

I strongly suspect some numbers (particularly the number '2') are being pressed by at least one of my controls without my knowledge, but I will get to the bottom of it eventually.

 

I think I will set all RC4 controls as a completely different set and make sure they are not used anywhere else - maybe Ctrl-Shft-F1 to Ctrl-Shft-F9 would be a better bet.

Anton,

 

What most of the time works for me is dialling the new freq in the standby, ack and then make it active.

 

John

Thanks John, I've only just realised I had been acknowledging immediately and then trying to dial, which was making it more difficult  

I would highly resist using any Fn commands in RC as they are used in many Win functions as well as FS and add-ons. In addition it can introduce timing errors in a sequence like that.

 

For flying in RC I would at least use one waypoint between airports and if in a jetliner a trip[ of at least about 200nm. This will avoid you getting over tasked with all of the add-ons running. For learning RC just run a default aircraft and RC going through the tutorials reading each first. When you are comfortable change to an advanced aircraft if you wish and in FS turn down ai aircraft for now.

 

When you are efficient in running the advanced aircraft you can bring the goodies one at a time on line that require interaction from you.

 

So, in order:

 

1. Be proficient on your aircraft and insure your hardware is set up correctly to control the aircraft.

2. Bring RC on line and run RC and FS without ai on in FS.

3. Turn on ai in FS and run FS and RC.

4. Try MCE and get used to that.

5. When proficient bring it all on

 

One step at a time to prevent brain overload.

Cheers ronzie, that's the way I have gone, and it is going much smoother now.

The biggest problem turned out to be my button box - I was using 6 buttons for RC4, and they were set as 1 to 5 plus a shift key, then I used the shift button to double them up as 6 to 0. But if I selected 7 (shift + 2), it turns out it was acknowledging the call AND selecting option 2 at the same time, hence the accidental calls for missed approach etc - strange as this method has worked fine every other time but no matter, I have remapped all keys today, removing any danger of conflict; also running reduced addons as you said; I am now up to RC4+MCE, with a few AI, and my flight from KLAS to KSFO went like clockwork.