I'm pretty sure I'm doing something wrong or misunderstanding the instructions in RC4, but I'm trying to figure out if I want to use MCE to communicate with ATC instead of using the RC4 copilot how do I do that.  I have two copilots, RC4 copilot and MCE copilot.  For now I simply use MCE for gear and flaps.  Should I just turn off MCE and use the copilot for RC4?  If I want talk to ATC myself, I'm not quite sure how to set up MCE so I can do that.  I for the most part fly a twin beechcraft and would like to try the radios myself.  I've seen videos on YouTube of guys using RC4 and MCE and it works great.

Problem solved

 

Great, but what was it, please?

13 hours ago, Tight Git said:

Great, but what was it, please?

Google "Voice Attack"

Thanks, but does that mean you had to buy the Voice Attack software to solve your problem?

15 hours ago, C130FE said:

Google "Voice Attack"

I'm afraid you've been given the wrong advice in another thread

People don't realize, we actually ship a tool called Voxkey which is like a free copy of VoiceAttack, only dedicated to flight simming.

It can be useful for people using VR, to free them completely from the need to look at the keyboard.

Start->All Apps->Multi Crew Experience->Voxkey

And more importantly, you won't be running 2 instances of the speech engine. Only one will cater for FO interaction and whatever custom commands you may have put in Voxkey to trigger things via keys.

VoiceAttack is more suited for other games. It simply translates your commands to key presses.

Unless you're looking for quick cheats to select options, neither VoiceAttack nor Voxkey are suited to RC4 for the following reason. .

You'd have to create speech commands tied to a specific call_sign and/or runway. Change that and nothing will work.

And what about variable things like runway?

Add how do you go about requesting a different runway, Altitude or direct to??

With MCE, you use proper ATC phraseoilogy

Ground KLM 143 requesting runway two five left for departure.

Assuming the runway exists, MCE will automatically select "-Req Rwy" in RC4 ATC menu, wait for the next set of available runway, go through them to see if there is a match and eventually move to the next screen. If there is a match, option is selected and next thing that happens is controller granting or denying request.

How would you do that with Voice Atack? 

You are cruising at FL 280 and you want higher or lower altitude.

Are you going to have commands such as "Request higher", then wait for the next set of suggested altitudes and say "select one" or "select two"??. Of course that's not ATC phraseology. These are examples of proper requests

Control KLM 143 request further climb flight level 310

Control KLM 143 requesting flight level 210

MCE will compare the curent altitude with requested one, delect "-Req Hi" or "-Req low" in ATC menu, wait for the next set of suggested altitudes and select the one that corresponds to the altitude difference.

Same with request direct to waypoint.

The proper ATC jargon goes like this.

Control KLM 143 would like to proceed direct to DENBO (you speak the word DENBO, not spell it). DENBO is a fictive waypoint along the flight plan.

For direct to VOR or NDB...

Control KLM 143 requesting direct course to Mike Romeo Victor  (where MRV is a naviad listed in flight plan)

And it works reliably thanks to MCE reading the flight plan assigned in RC4, fetching the waypoints and feeding them to speech engine so it can recognize them easily. Giving the speech engine 25000 possible waypoints and expecting it to get it right is wishful thinking.

So, there you have it. A very neat interface to Radar Contact ATC, that tries to teach you proper ATC procedures and doesn't require creating hundreds of custom commands that only work with a specific callsign or runway.

If you want the same MCE FO to handle RC4 ATC, be aware, there are now 4 MCE co-pilots that can do that. 

William, Lorna, Stuart and Robert co-pilots have recorded audio for RC4. You can download their recordings from this link

Instructions are included. Basically, need to backup some of the voices folders in RC4 installation folder, and replace the audio within.

That way, the same MCE FO voice will be managed by RC4 as if it was one of its stock voices.

 

 

 

On 11/26/2017 at 7:55 AM, FS++ said:

I'm afraid you've been given the wrong advice in another thread

People don't realize, we actually ship a tool called Voxkey which is like a free copy of VoiceAttack, only dedicated to flight simming.

It can be useful for people using VR, to free them completely from the need to look at the keyboard.

Start->All Apps->Multi Crew Experience->Voxkey

And more importantly, you won't be running 2 instances of the speech engine. Only one will cater for FO interaction and whatever custom commands you may have put in Voxkey to trigger things via keys.

VoiceAttack is more suited for other games. It simply translates your commands to key presses.

Unless you're looking for quick cheats to select options, neither VoiceAttack nor Voxkey are suited to RC4 for the following reason. .

You'd have to create speech commands tied to a specific call_sign and/or runway. Change that and nothing will work.

And what about variable things like runway?

Add how do you go about requesting a different runway, Altitude or direct to??

With MCE, you use proper ATC phraseoilogy

Ground KLM 143 requesting runway two five left for departure.

Assuming the runway exists, MCE will automatically select "-Req Rwy" in RC4 ATC menu, wait for the next set of available runway, go through them to see if there is a match and eventually move to the next screen. If there is a match, option is selected and next thing that happens is controller granting or denying request.

How would you do that with Voice Atack? 

You are cruising at FL 280 and you want higher or lower altitude.

Are you going to have commands such as "Request higher", then wait for the next set of suggested altitudes and say "select one" or "select two"??. Of course that's not ATC phraseology. These are examples of proper requests

Control KLM 143 request further climb flight level 310

Control KLM 143 requesting flight level 210

MCE will compare the curent altitude with requested one, delect "-Req Hi" or "-Req low" in ATC menu, wait for the next set of suggested altitudes and select the one that corresponds to the altitude difference.

Same with request direct to waypoint.

The proper ATC jargon goes like this.

Control KLM 143 would like to proceed direct to DENBO (you speak the word DENBO, not spell it). DENBO is a fictive waypoint along the flight plan.

For direct to VOR or NDB...

Control KLM 143 requesting direct course to Mike Romeo Victor  (where MRV is a naviad listed in flight plan)

And it works reliably thanks to MCE reading the flight plan assigned in RC4, fetching the waypoints and feeding them to speech engine so it can recognize them easily. Giving the speech engine 25000 possible waypoints and expecting it to get it right is wishful thinking.

So, there you have it. A very neat interface to Radar Contact ATC, that tries to teach you proper ATC procedures and doesn't require creating hundreds of custom commands that only work with a specific callsign or runway.

If you want the same MCE FO to handle RC4 ATC, be aware, there are now 4 MCE co-pilots that can do that. 

William, Lorna, Stuart and Robert co-pilots have recorded audio for RC4. You can download their recordings from this link

Instructions are included. Basically, need to backup some of the voices folders in RC4 installation folder, and replace the audio within.

That way, the same MCE FO voice will be managed by RC4 as if it was one of its stock voices.

 

 

 

All of these things you said are true.  It's a cool program.  But, in the last month, I've spent 90% of my time trying to get it to work and 10% of my time flying.  I want to fly.  Not trouble shoot.  I've finally found something that works.  Not as good as MCE would be IF I could get it too work.  But now I'm having a fun flying with ATC.  No trouble shooting, just flying.  Maybe sometime in the future I will try MCE again, but for now I'm satisfied with what I have.  I appreciate the support I've gotten from you Gerald.  

Rodger