On 7/7/2021 at 7:00 PM, FS++ said:

It did happen in much earlier versions that are using the Lvar interface. Should be settled by now.

A restart of MCE mid-flight should get it going in the odd case this happens.

I assume you have "mce.exe" V2.9.3.0 as well as "Simco64_Ldr.exe" V2,0.1.6 in \Multi Crew Expeience\ installation folder.

Which plane are you using?

Which livery if any. Perhaps a download link for livery would help too. You never know with these.

Are you using FSUIPC?

 

The last version I saw on the download page was 2.9.2.9 and do I have to download Simco64_Ldr.exe separately?  I was using the tbm 930 with mugz improvement mod, today I did 2 flights with longitude standard livery and had no issues. Yes, using fsups .

 

7 hours ago, Jerry_2083 said:

The last version I saw on the download page was 2.9.2.9 and do I have to download Simco64_Ldr.exe separately?  I was using the tbm 930 with mugz improvement mod, today I did 2 flights with longitude standard livery and had no issues. Yes, using fsups .

If it's working right now and the TBM is your main plane, no need to update.

Update is mostly to keep in synch with changes made to FlyBywire Developer edition (which changes at least once a week). Also adds support for CS 777 in MSFS.

When you do have to update, get the patch

Unzip, then manually replace "mce.exe" and "Simco64_ldr.exe" in main \Multi Crew Experience\ installation folder as well as the files in \Multi Crew Experience\CandC\ folder.

You can always request a link to an older version from support in the odd case the most recent version changed things for the worse on your side.

 

FYI,

Download link to 2.9.3.0 does not seem to be working. When attempting to download, I received download.html

Tony J

The download link is broken and the same problem manifested in the Cessna Longitude

Would it help to put he patch in 2.9.2.9?

With pf3 the traffic information is not being rogered.

In the pmdg NGXu the "set takeoff flaps" command (in voxscript) is not being recognized. PMDG T7 is working, PMDG 747 not tested)

Used to work in 2926.

I'm now on v2940, p3dv4.5

 

Best regards

Edited November 6, 20214 yr by starter

35 minutes ago, starter said:

With pf3 the traffic information is not being rogered.

In the pmdg NGXu the "set takeoff flaps" command (in voxscript) is not being recognized. PMDG T7 is working, PMDG 747 not tested)

Used to work in 2926.

I'm now on v2940, p3dv4.5

 

Best regards

You mean PF3 clearances to you not acknowledged.

Go to \PF3\ installation folder and open "PF3_MCE.ini" and ensure Active=1

It only happens when Fo is in charge of ATC, in  case you took over ATC, tell him he has ATC again.

Other thrings that could throw it off, the odd call_sign showing up in caption and MCE not seeing it as your callsign.

Could you post some of the lines in "Clearance.log"? Thanks

 

Gerald,

i mean when flying and traffic comes near to you, you'll get from atc a: callsign traffic at xxx o'clock, xxx miles, heading xxx.

My copilot used to respond then with : roger, traffic in side or something similiar. This is not happening after v2926 anymore.

 

Best regards

 

On 2/2/2021 at 6:56 AM, djxmdjxm said:

Hi all, I still have this problem (tested on TBM930). When I say "set altimeter to 3012" my FO just scrolls all the way down to 2900 with the obvious implications to altitude. 

Does anyone else have this problem? Thanks!

Good morning. I too am having the same issue with my CRJ profile. It seems to work on my Baron 58 profile though.

I am also having numerous issues with my FO when using the CRJ. I will ask FO to perform an action [":Turn beacon on" or "Turn battery on" or any command for that matter and FO responds correctly, but nothing happens.

I've tested with the Baron 58 and all seems to work fine there.

Also, when I start the program, it starts the Mic setup wizard every time. Is that normal?

MCE Ver 2.9.42

1 hour ago, deltgam88 said:

I am also having numerous issues with my FO when using the CRJ. I will ask FO to perform an action [":Turn beacon on" or "Turn battery on" or any command for that matter and FO responds correctly, but nothing happens.

I've tested with the Baron 58 and all seems to work fine there.

Also, when I start the program, it starts the Mic setup wizard every time. Is that normal?

MCE Ver 2.9.42

I assume we are talking Prepar3D or FSX as these are the sims where the mic wizard is started once a day. This is to prevent Windows randomly reducing audio level of background applications like MCE, PF3, VoxATC, Radar Contact etc....

Please confirm simulator used for futher guidance.

 

MSFS 2020

MCE ver. 2.9.42 - Asobo CRJ

1. Mic setup wizard opens on every launch.
2. [MCE] Looking for changes to current aircraft, then MCE ready!
3. Then same issue "Could not detect aircraft... possibly flight sim reloading", once it shows up it does not go away. 
4. FO responds to checklists, flows and orders, but never does the task. "Set altitude to FL250", FO responds and then comes back with "Set!" Nothing happens!  This is with every command I issue, FO does nothing, but talk back.

Beech B58

1. Ask FO to set altimeter to "29.95" or any setting and it sets to "27.99"

 

 

 

 

20 hours ago, deltgam88 said:

MSFS 2020

MCE ver. 2.9.42 - Asobo CRJ

1. Mic setup wizard opens on every launch.
2. [MCE] Looking for changes to current aircraft, then MCE ready!
3. Then same issue "Could not detect aircraft... possibly flight sim reloading", once it shows up it does not go away. 
4. FO responds to checklists, flows and orders, but never does the task. "Set altitude to FL250", FO responds and then comes back with "Set!" Nothing happens!  This is with every command I issue, FO does nothing, but talk back.

Beech B58

1. Ask FO to set altimeter to "29.95" or any setting and it sets to "27.99"

 

 

 

 

Go back to downloaded unzipped file and look under \Rwsources\FilesMSFS\

Copy <fsuipc-lvars-module> and paste it to \Community\ folder, overwriting whatever is there.

Make sure you set the Aerosofty CRJ as the plane MSFS loads on starup.

See document Start->Multi Crew Experience->Using MCE with FS2020

Start MSFS, wait until CRJ is on tarmac. Only then start MCE (not while setting up the flight)

Should get you going with CRJ. If not, could be some livery that's causing MCE not to properly identify the plane. Use default Aerosoft livery and send download link for the livery youi're using if it's causing the issue.

Will check the B58/ I assume you're not using any mod for this plane.

 

 

Edited December 18, 20214 yr by FS++
typo

Thank you and correct, no mod on the B58 other than the included liveries.

 

Hello All,

I'm having trouble getting MCE to correctly acknowledge "...runway in sight". MCE always send "...Runway NOT in sight".

I use MSFS 2020 and MCE with native ATC.

I have MCE build 2.9.4.2.

My IFR flight plan is SCEL->LINER->SCRG

Center assigns me visual runway 03, via vectors (@SCRG). When I acknowledge the approach, MCE interprets my voice correctly and responds with the correct native ATC response.

However, when the time comes, I tell Center I have the runway in sight. MCE incorrectly sends the runway NOT in sight response.

I have tried:

Center, 9KQ, we have the runway in sight.

Center, 9KQ, has visual on the runway.

Center, 9KQ, runway 03 in sight.

In all of the three attempts above, MCE displays the red text correctly (my voice), but sends the runway NOT in sight response for native ATC.

I believe either of the three responses above to Center should work correctly...

Edited December 28, 20214 yr by flyblueskies