FS++

Strange... I assume you replaced all files from the path and that the speech command is written in all lowercase as "select takeoff flaps", not "Select takeoff flaps". This can happen when you add commands in Notepad. The MCE UI always enforces lower case characters

Agree. That specific checklist (final cockpit preparation) wasn't handled properly. Next patch should get it sorted hopefully this evening. Edit: Won't be ready until next Monday. Sorry for that.

As Burge suggested You may have enabled option "Enable nagging" in "Advanced options" panel by accident. That's when FO wants you to stick within limits as set in Proficiency level, like keeping speed within 5-10 knots of autopilot target when flying manually. The feature is disabled by default. If you haven't updated MCE for a while, I suggest you un-install previous version via Windows control panel, don't delete anything manually, then download latest: http://www.multicrewxp.com/Downloads.html To make sure you have a config file that's in synch with latest options, restore MCE to factory settings Windows Start->Multi Crew Experience->Restore factory settings. That will force you to go through the wizard again. Please do so. No need for speech training though.

Seems to be related to speech engine not handling the submitted MCE grammar for this particular command. Try "select takeoff flaps". I have it working. The other command should work too but will require revised files in \CandC\ folder.. Speech grammar will be revised to allow even more speech variations like "set planned takeoff flaps", "set the flaps for takeoff", etc....

Thank you for valuable feedback. There is no way for FO to read checklist on-screen status to find out if it's pending or completed. That's why he always goes through the list. We found that in some instances, FO was missing an additional validation click (Notably for "before takeoff checklist" (possibly why it still says pending) and "after takeoff checklist".(where there is a secondary menu (all engines running vs engine failure before you get to the actual checklist) Re-download patch and replace all files and try again. Are you guys interested in having ATR checklists that include "abnormal procedures" so we can train the FO for those?

I guess, that's why we call it "The wizard" 😛 I am writing this to anyone else who may experience startup issues. For smooth operation that won't need fiddling with any Windows settings... 1 - Always install MCE to default path (C:\Program Files (x86)..folder and never mess with that folder's permissions. It will only take about GB max including all additional recorded voice packs. 2 - Ensure you have the correct key for the machine ID 3 - Eventually, tell your anti-virus to trust "mce.exe". It is digitally signed, but because it's protected and AV cannot analyze it, some may throw a "false positive" out of caution. 4 If the above doesn't do it, go to C:\Users\your_user_name\AppData\Roaming\Multi Crew X-Plane\ folder, open "xpmce.ini" in Notepad and ensure "Debug=1". Start MCE and it should generate a "startup.log" in that same folder. Send it to support in order for us to work out where it stalled.

Somehow broke some time ago. Redownload patch and just replace "mce.exe" V3.0.6.7 Should work now. If using MSFS, also replace Simco64_Lder.exe and files in \CandC\ folder

Indeed. Can't remember if the CS 757 has a "available commands" list. Will post one eventually. The pre-made flows give you an idea. Lots of undocumented features. For instance... It's possible to teach the crew to understand and act on ANY natural speech you may want to come up with, including non-English languages. That's because we built a speech simulator into MCE. Not found in any other similar products. Since last year, it's possible to warp the aircraft in MSFS, P3D or FSX to any airport/gate/runway using voice commands such as Move the plane to Frankfurt gate twenty one Relocate the plane to las Vegas (takes you to first gate) position aircraft at Kilo Julliett Foxtrot Kilo runway zero four left. Within same airport can relocate t another runway with these move the plane to runway zero seven left warp the aircraft to runway two five right. As is the case with all critical items, there will always be a vocal prompt to confirm the command is intended. By default, keeping silent for about 10 seconds means "no, ignore last command". And if it's dark out there afterv relocating and can't be sure where you are, ask copilot "confirm position". Most dialing commands can be re-adjusted on the fly.. Example: you ask the FO "set heading one fifty". Let's pretend speech engine picked-up "set heading one fifteen" by mistake. Co-pilot starts dialing. No need to wait for him to dial the wrong one, then make a second command to get him to set the correct one. while he's dialing the wrong one, just say "correction one five zero", "my bad one five zero", "sorry one five zero", "my mistake one five zero" and he should dial the correct one. Once dialing is complete, you would need a new speech command. Same for speed or altitude dialling. No need to mention "altitude", "heading" or "speed", he knows which item he's currently dialing.

Let me know if it's still hit and miss. You may want to check Windows defender history to see if at any time in the past, it flagged "mce.exe" as potential malware, which means it may occasionally prevent it running. find the reference to the incident and select <<Action> "Allow on device".

You're welcome. Give the speech command "set takeoff flaps" verbally and see if it's recognized. Normally, it's enabled for all planes. For those where MCE can read actual takeoff flaps like most PMDG planes, Fo will set the flaps as per CDU input. For others, he just sets what's in the MCE panel. First detent if user didn't change it..

This V3.0.6.6 patch should address most items you reported. Thanks for doing that. For instance, strobe light was previously tied to a custom variable of the plane which now uses MSFS stock variable for this specific item. There are new commands for the oxygen main supply switch.

Thanks. In the end, that wasn't the issue. This patch should address your issue

A new patch has been uploaded, mostly to address minor issues with ATR support. I suggest you grab it from this link Your security software will see it as a new file.

Sorry to hear that. I suggest the following... Un-install previous version via Windows Control Panel, add-remove programs. If you're on Ultimate Edition, download latest V3.0.6.4 from main website http://www.multicrewxp.com/Downloads.html If on MSFS Edition, use download link sent to you by support (available on request) or get latest from your Simmarket account. Install to default path and ensure your activation file is present in \Multi Crew Experience\ installation folder. No need to patch. If it only runs AFTER re-installing, chances are your anti-virus is blocking or moving "mce.exe" to the Vault. Tell it to trust the file, it's digitally signed anyway. Some anti-virus packages like Avira or Avast do that. The major ones usually don't. Then report regarding V3.0.6.4

Just when we were about to post a patch, I just learned that a new ASOBO ATR package has been released a few days ago. Therefore, will be pushed by a few more days

As things stand in V3.0.6.4, the only planes where Fo is expected to receive a command to press EICAS status are.. PMDG 777 (in both P3D & FSX) PMDG 747 i8 (in both P3D & FSX) Quality Wings 787 (in both P3D & FSX) ASOBO 787 (MSFS) Captain Sim 777 (in both P3D & FSX) Pheonix 777 (in FS9) Therefore, it's a mystery as to why it's happening with the CS 757. It could be a case of "mistaken identity", maybe the plane isn't seen as to what it is. The CS 757 is fully supported and the FO is expected to handle pretty much any switch or dial. Could you please open "aircraft.cfg" and post the following sections.. [fltsimX] sim=whatever_is_there. It's not uncommon when CS releases a new variant (that we don't have or tested against) and the "sim=whatever_that_is_not-expected" causes MCE to see it as default plane or maybe some other CS plane. Only aircraft items that use default MSFS, Prepar3D, FSX variables would then be under FO's control and many overhead panel switches commands may not be available for speech reco as they are only enabled based on which plane is detected.

There will be a patch in the coming days.

Prepar3D or FSX?

I may have misunderstood the issue and yes aware 757 doesn't have ECL. Does your custom checklist have an item that mentions "eicas status" or something like that. FO is trained to handle those as well as "recall" to press relevant buttons when he comes across them. It can be removed for 757.

Welcome aboard.Balint It's automated behavior. Once a checklist is done with, it's best to set the screen to STS. He does that with all supported planes that have an ECL Make sure you read this New User Questions - The Multi-Crew Experience (MCE) Support Forum - The AVSIM Community And this Command for terrain radar - The Multi-Crew Experience (MCE) Support Forum - The AVSIM Community They apply to all fully supported planes.

The automated disabling of the voice fading was the result of users complaining in this thread. Instead of giving instructions to follow, the scripted clicking would do the job CoPi voice volume turns down - The Multi-Crew Experience (MCE) Support Forum - The AVSIM Community You can disable it in "mce.ini" by adding/editing this line to [OPTIONS] section [OPTIONS] DisableVolumeFade=1 Andy, I'm not doubting your report about inability to start. Just saying, If it was that unreliable, we would be swamped with such reports for all editions and the Demo would be a disaster. From experience, there are 2 scenarios where MCE may exhibit strange behavior when you exclude other software protection related no-starters. 1 - A user modifies C:\Program Files (x86)\ folder permissions. Never a good thing to do. For instance, when MCE starts it needs to fire both Simco64_Ldr.exe as well as the Splash screen (Splash.exe). Believe it or not, Windows may not grant permission for "mce.exe" to do that. It does under "default user rights" and requires "mce.exe" to be digitally signed. See this thread: Could not start Splash Screen - The Multi-Crew Experience (MCE) Support Forum - The AVSIM Community Although it's possible to install MCE outside C:\Program Files (x86)\ we recommend default path so you won't be instructed to disable Windows UAC or mess with other settings. Default path is better and won't take more than 2 GB space even with all recorded audio voice packs installed. 2 The other unknown variable is anti-virus. Since MCE has built-in protection, some anti-virus may wrongly see it as potential malware and will block the process. Maybe something we don't know happens when the software is just installed. At the very least, go into your anti-virus program settings and ensure you exclude "mce.exe" from "process monitoring" (not to be confused with excluding folder for scanning). I mean, the AV shouldn't kick in when the process is started. Avira and Avast used to do that. The file is digitally signed, not coming from "unknown publisher". You can submit it to VirusTotal website which checks it against about 72 packages and you will notice there are at least 4 or 5 that may wrongly flag it as "possible malware" (and likely block it), but the vast majority doesn't these days. Finally, as I acknowledged many times before on this forum, it's not impossible with all those fast and furious updates, occasionally things get screwed up. But, based on sales (following Demo) and e-mail reports, it doesn't appear to be the case with version 3.0.6.4 If anyone else has trouble starting MCE MSFS edition (Or any other edition for that matter), please report in this thread. Thank you

Thanks for the report. Indeed, Magnar videos were very useful. Switches will be looked at. As far as the checklist is concerned, the FO makes no assumption as to which checklist was run before and just moves to next one. He's supposed to always bring up the main menu for various checklists, scroll down through them to select the correct one. Obviously, the scrolling is done with the assumption all the existing lines in menu are known, otherwise, he would select the wrong one. Maybe this has changed in airplane update (perhaps new menu item inserted). It's certainly a useful feature that must be addressed. Hydraulic pump aux push will be a hit an miss because while it responds to Mouse held down long enough works, controlling it via Lvar is tricky so can't guaranteed that.

Thanks for reporting. It's a separate issue from the one that initiated this thread and fixed since. The Simbrief feature should otherwise work fine now when "One drive" isn't involved. This will be looked at.

If it's using the same switches as default plane, it would be just a matter of letting MCE treat it as such. Set "Debug=1" in "xpmce.ini", With the plane loaded, start MCE and it should display info it gathered about the plane. Send screenshot info to support or post picture here. Thanks

When using default human recorded voices, you may come across some verbiage that wasn't recorded and you need to use alternatives like "flight deck cabin crew briefing", The other option is to get a high quality TTS voice, assign it to your FO voice and you could write pretty much anything and will always be read. Checks on multiple items on same line aren't recommended as the Fo needs to determine from the left side of the line which exact item needs to be checked. Either pumps or crossfeed valve. Try 'mains on cross-feed closed' without the '_' character and he will likely check pumps only. For "Anti-ice" since FO checks that item, instead of using '_', write "as required", you could then reply "as required", "as desired" and FO will assume you want switches left as they are. Or reply ON (or equivalent words) and he will ensure they're ON, or reply OFF (or equivalent words) and he'll make sure they are off. As for "now said" it's actually "now set". That happens when you have checklist option "strict" enabled. In that case, instead of constantly challenging you on same items, he'll challenge once, then try to set the switch as per checklist (and say "now set". It could also be an indication your microphone isn't calibrated properly, causing FO to hear "replies". Will run a test on those items and see what happens as soon as possible.