Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Still having problems

Featured Replies

  • Author

If you wanted runway 22R, say

 

“Ground Canjet 1976 requesting runway 22R for departure”

 

“Ground Canjet 1976 requesting runway 22R for takeoff”

 

“Ground Canjet 1976 would appreciate runway 22R for departure”

 

“Ground Canjet 1976 would appreciate runway 22R for takeoff”

 

 

MCE will then trawl the RC4 menu, until it comes across runway 22R and selects it.

 

Needless to say if you say…

 

“Ground Canjet 1976 requesting runway 22 for departure”, you’ll see the runways menu scrolled but nothing will happen simply because there is no runway 22 for departure. It’s either 22L or 22R.

 

 

It does do that but does not select a runway it just stops, and I still can't contact any controllers after ground, ie tower, departure, center. Anyways thanks for the compatibility issue advice, I was trying different things yesterday. Anyways is there a chance I could get my hands on the previous version just to try it out, Ya never know.

 

edit are there any issues with running this in fullscreen mode?

 

 

  • Author

And hear is another example of how things are not working, Im on the ground at CYQM, contacted ground for my IFR Clearance, no problem, requested for push and start no problem, now Im tying to request taxi, "Ground Westjet 433 ready to taxi" it shows up on my screen in red, I try it over and over again, nothing, just a 1 on the screen with Ground on 121.80, which Im dialed into, so now I decided to push the button on my KB, nope wont work, so then I try to use the voice commands mentioned tto select an item from the menu, nope they don't work either, so its completely stuck, it always goes unresponsive, so what else can I do, I wish another RC4 user could chime in and tell me what version they are using and if they are having any issues.

 

 

  • Commercial Member

And hear is another example of how things are not working, Im on the ground at CYQM, contacted ground for my IFR Clearance, no problem, requested for push and start no problem, now Im tying to request taxi, "Ground Westjet 433 ready to taxi" it shows up on my screen in red, I try it over and over again, nothing, just a 1 on the screen with Ground on 121.80, which Im dialed into, so now I decided to push the button on my KB, nope wont work, so then I try to use the voice commands mentioned tto select an item from the menu, nope they don't work either, so its completely stuck, it always goes unresponsive, so what else can I do, I wish another RC4 user could chime in and tell me what version they are using and if they are having any issues.

 

If it's not responding to manual keyboard input you may want to have a look at your network setup and potential issues with latencies. Suggest you send your "rcv3.dat" file found inside RC4 installation folder to Support.

 

Meanwhile...

 

With regards talking to other controllers, the workflow should be more or less as follows.

 

Dial new frequency

Establish Contact with next controller

Exchange a few messages with current controller

Acknowledge handoff

Dial next frequency

Establish Contact with next controller

Exchange a few messages with current controller

Etc…

 

Perhaps you’re used to the “Tune on contact” option in RC4 which isn’t realistic.

 

Normally with FO enabled you would just need to say…

 

“Going to tower”

“Tune tower on COM 1”

“Dial Centre on VHF1”

“switching to approach”

etc…

 

and the frequency will be set for you.

 

Since you aren’t using the FO, you’ll have to make sure you’ve got the frequency dialled prior to transmitting, and according to your statement above you did.

 

There is also this controller nagging (about contacting next controller) happening too quickly and well familiar to Radar Contact users.

 

Sure, you can have a go at the previous version, but you need to proceed exactly as follows…

 

Un-install previous version

Download (save to your desktop) older version from this link:

 

http://www.multicrewxp.com/mce2494.zip

 

Unzip downloaded file, and run “setup”.

 

When done, check fsInsider.dll inside FSX folder is the same version as the package you installed (in this case 2.4.9.4.

 

Restore to factory settings in order for the mce.ini config file to be in synch with previous version.

 

Finally, be aware that the older version has restrictions on which keyboard keys can be assigned via RC4 settings (refer to manual). Example: Keys 0 to 9 shouldn’t use CTRL or SHIFT keys.

 

This restriction has been lifted in the latest version.

  • Author

Sure, you can have a go at the previous version, but you need to proceed exactly as follows…

 

I have terrific news Gerald installed v2.494 fired it up and not one single problem, I did not change the way I approached things for the most part I was doing it right. Contacted every controler form Moncton NB to Toronto ON, request different runways and flight levels, not one glitch or hiccup, where as with the 2.5 I could not even get on the tower freq or use my KB before everything would stop responding.

 

 

  • Commercial Member

I have terrific news Gerald installed v2.494 fired it up and not one single problem, I did not change the way I approached things for the most part I was doing it right. Contacted every controler form Moncton NB to Toronto ON, request different runways and flight levels, not one glitch or hiccup, where as with the 2.5 I could not even get on the tower freq or use my KB before everything would stop responding.

 

OK, thanks for feedback Ian.

 

I call on every MCE user who runs RC4 regularly to confirm whether the latest version had any negative impact on that aspect of the application, or just normal operation as usual.

 

Thank all.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.