I completed two flights today with the newest MCE version (the one I downloaded via the latest patch link in the Fenix A320 topic). A few issues I have found:

• F/O doesn't reset the stab trim
• Rudder trim reset doesn't work
• During the checklist the F/O confirms "now set" for gear down even though it was down already; same for the APU (off) and probe heat (auto) during checklists
• The guard for pax oxygen is left open when the F/O checks the switch position
• At 60 kts on rollout, the F/O calls out "60 kts, reverse green" where reverse green obviously occurs at the wrong point
• This is a bit of a biggie since it's one of the most useful callouts: The "autobrake disarm"/"brakes active" callout is missing

Other than that I have two suggestions:

• F/O control for the right side (F/O) stopwatch (instead of the Captain's)
• Vspeed callouts earlier: The F/O calls out the Vspeeds on takeoff a little late/when the aircraft is already several knots past the speeds. Maybe this can be adjusted so that MCE reads the speeds to be a few knots below the actual speed so that the callouts occur right at the speeds? I don't know if this is easily doable though.

Everything else works fine as far as I can see and given PMDG have finally released the SDK I'm hoping this may be the last update for a long time (unless they change something that affects MCE). 

@FS++ It seems MCE doesn't work with the PMDG 737-800. I flew two flights in the 700 as mentioned and with the exception of the above it worked fine. In the 800 though MCE doesn't work right. It can't read MCP windows and therefore sets wrong values and the ground services notification takes a long time to come up. Recognition of the power state of the aircraft to determine which FMC to use also doesn't work (FMC 1 is used instead of 2). It seems MCE can't read the aircraft.

Edit: Forget that. I noticed the [SDK]EnableDataBroadcast=1 line wasn't in the options.ini file for the aircraft. I readded it and it works again. Although I don't understand why MCE worked fine with the 700 that also had the line missing but not with the 800.

Perhaps my findings in the OP were caused by the line missing from the options file. I'll check on my next flight.

Edited October 25, 20223 yr by threegreen

42 minutes ago, threegreen said:

@FS++ It seems MCE doesn't work with the PMDG 737-800. I flew two flights in the 700 as mentioned and with the exception of the above it worked fine. In the 800 though MCE doesn't work right. It can't read MCP windows and therefore sets wrong values and the ground services notification takes a long time to come up. Recognition of the power state of the aircraft to determine which FMC to use also doesn't work (FMC 1 is used instead of 2). It seems MCE can't read the aircraft.

Probably because the plane isn't properly identified.

Could you post the [fltsim.X] sections in "aircraft.cfg" for the 800 series?

Are you by any chance using a livery that wasn't made by PMDG?

What is the installation path for the new variant?

Thanks

Just now, FS++ said:

Probably because the plane isn't properly identified.

Could you post the [fltsim.X] sections in "aircraft.cfg" for the 800 series?

Are you by any chance using a livery that wasn't made by PMDG?

What is the installation path for the new variant?

Thanks

See the added portion of my post. Turns out it was because the SDK broadcast line was missing.

20 minutes ago, threegreen said:

See the added portion of my post. Turns out it was because the SDK broadcast line was missing.

Remember, there is the older Simco64_Ldr.exe which could interface the plane without reading anything (EnableDataBroadcast wouldn't matter in that case) and the new one that relies on SDK and MUST have this

[SDK].

EnableDataBroadcast=1

Does the 800 have a separate options file or is it the same?

 

Edited October 25, 20223 yr by FS++

30 minutes ago, FS++ said:

Remember, there is the older Simco64_Ldr.exe which can interface the plane without reading anything (EnableDataBroadcast wouldn't matter in that case) and the new one that relies on SDK and MUST have this

[SDK].

EnableDataBroadcast=1

Does the 800 have a separate options file or is it the same?

 

I'm using the latest MCE that relies on the PMDG SDK. I pasted the same line into both aircraft files and the 800 works now. I hadn't however pasted the line into the 700 when I flew it a few days ago (same, latest Simco64_Ldr.exe) and it worked nonetheless. Every 737 variant has its own options file since they are sold separately.

3 hours ago, threegreen said:

I'm using the latest MCE that relies on the PMDG SDK. I pasted the same line into both aircraft files and the 800 works now. I hadn't however pasted the line into the 700 when I flew it a few days ago (same, latest Simco64_Ldr.exe) and it worked nonetheless. Every 737 variant has its own options file since they are sold separately.

With the 700 series settings file is in this path.

"C:\Users\user_name\AppData........\\Microsoft Flight Simulator\\Packages\\pmdg-aircraft-737\\work\\737_Options.ini"

Which path is there by default for the 800? Thanks

Edit: Keep in mind, if you re-install the plane, it's likely the SDK entry will revert to disabled, in which case you either re-install MCE to get the file edited automatically, or manually add the lines as you did.

Edited October 25, 20223 yr by FS++

On 10/25/2022 at 6:55 PM, FS++ said:

Which path is there by default for the 800? Thanks

Same path except swap pmdg-aircraft-737 for pmdg-aircraft-738.

Just completed another flight in the 800 and MCE works just like in the 700, with the exception of what I posted above.

thats exactly the same prob i reported with su11, now can you please explain this work around in details for the -800 and fenix 320?

thanks

2 hours ago, ayousry said:

thats exactly the same prob i reported with su11, now can you please explain this work around in details for the -800 and fenix 320?

thanks

Get this patch and just replace "Simco64_Ldr.exe" in \Multi Crew Experience\ installation folder.

http://www.multicrewxp.com/Latest-Beta.zip

It's also patched to handle FCU with FENIX A320 most recent release (V139).

 

15 hours ago, threegreen said:

Same path except swap pmdg-aircraft-737 for pmdg-aircraft-738.

Just completed another flight in the 800 and MCE works just like in the 700, with the exception of what I posted above.

Thank you

On 10/27/2022 at 1:53 AM, FS++ said:

Get this patch and just replace "Simco64_Ldr.exe" in \Multi Crew Experience\ installation folder.

http://www.multicrewxp.com/Latest-Beta.zip

It's also patched to handle FCU with FENIX A320 most recent release (V139).

Does this include any updates to the 737?

42 minutes ago, threegreen said:

Does this include any updates to the 737?

For most updates, unless advised to do a full re-install, it's usually 2 files you need to be aware of.

For anything to do with speech reco, Fo audio or program logic ensure you replace "mce.exe"

For anything to do with aircraft switches and dials status, replace "Simco64_Ldr.exe".(latest version is V2.1.13 (caters for all supported aircraft in MSFS).

That's why it needs to be patched frequently. All it takes is a single switch to be mishandled by FO on any plane to warrant a new file.

Recent code refactoring required to make aircraft interfacing more manageable, as more are interfaced all the time, caused the pushback feature to get broken for Aerosoft CRJ very recently. New file uploaded today addresses that.

Please do not hesitate to report any glitch.

 

I'm having a blast with my scripts thank you MCE.

MSFS V2.9.8.3 PMDG737-700

I use the best TTS voices CereProc & IVONA & i use Balabolka reader to make my wav  files

ok how can get my FO to say Pilot & not pitot 

FO says pitot for probe.as well

nav light to strobe and steady that fine but will not activate the strobe light

logo lights not working

cheers Barry

13 hours ago, Burge said:

I'm having a blast with my scripts thank you MCE.

MSFS V2.9.8.3 PMDG737-700

I use the best TTS voices CereProc & IVONA & i use Balabolka reader to make my wav  files

ok how can get my FO to say Pilot & not pitot 

FO says pitot for probe.as well

nav light to strobe and steady that fine but will not activate the strobe light

logo lights not working

cheers Barry

Good to hear that.

I believe Ivona voices have an option to adjust pronunciation of specific words.

Go to C:\Windows\SysWOW64\Speech\SpeechUX\

Run "sapi.cpl" and it will list all 32 Bit voices found on your system. Select the Ivona voice you'd like to adjust and look for "properties", "Lexicon" or things like that.

To catchup with latest changes, download this patch and this time replace "Simco64_Ldr.exe" only

http://www.multicrewxp.com/Latest-Beta.zip