FS++

The Notify=whatever_sentence are made by the FO so you can hear what he's requesting. You need to add the actual commands that get Mechanic to respond or do things. Same sentence without "Notify". Notify=cockpit to ground nothing from mec cockpit to ground pause=10 Notify=ground connect ground power nothing from mec ground connect ground power The Notify statements are there for realism. You don't need them if you are yourself trying to extablish contact with mechanic with some elaborate speech that MCE doesn't expect, You could then have a custom flow triggered by your unique way to establish contact with mechanic like "hi there we need some juice on the bird" (or whatever you want), and won't need the Notify statement since the mech is expected to perform those tasks that are part of the flow.

Interaction with Ground mechanic and cabin crew are mostly spech based, rather than a speech command that triggers a button call. What you need to be aware of is whjat they can do. Goround mechanic can. First, before you can interact with ground mechanic, you need to establish contact with any of these cockpit to ground ground from flight deck mechanic from flight deck ... many other variations. The mechanic will be ale to... set wheel chocks (he'll do that automatically when you get in touch with him or about to pushback) Open or close cargo doors. Either automatically when GSX carts arrive or boiarding is complete for loading/unloading or on request with "mechanic open cargo doors", "ground engineer close cargo doors" connect/disconnect ground power. Use commands "ground mechanic connect ground power", "mechanic remove ground power". handle pushback. Depending on whether GSX is running in which case he transfers you to GSX operator, or will do that himself. Do not forget to ask him to disconnect when you no longer need him. "ground you may disconnect", "ground you may leave"....etc Therefore an example of a flow where the Fo extablishes contact with mechanic may look like this service interphone on Notify=ground from flight deck (add a Notify statement so you can hear the Fo making the request. Not required though) ground from flight deck (the actual command that gets the mechanic's attention) pause=10 (gives time to ground mechanic to repond) Notify=ground connect gpu (again, this is so you can hear the Fo requesting gpu) ground connect gpu (the actual speech command to rrequest GPU) pause=10 (need to insert some delay to give mechanic time to actually comnect GPU) ________________________ Regarding cabin crew... They can open/close doors on request with cabin crew open service doors flight attendants close serive doors cabin crew close all doors (to ensure no door is left open) cabin crew open doors (for boarding where they will typically open the front left door). They can also respond to GSX request to open whatever door. They also repond to flight deck crew notifications like flight attendants prepare for gate departure cabin crew get ready for takeoff cabin crew prepare for landing. cabin crew please proceed to flight deck. The human recorded voice packs for pursers are limited so you cannot have them say anything else unless you assign a TTS voice to them and can build all sorts of verbal interactions. Now keep in mind most people would probably not bother to memorize some of the trigger sentences I listed above. Since MCE has a "built-in speech simulator" (not found in any similar product), you could interact with both mechanic and cabin crew in the most natural way by creating custtom verbiage that you tie to built-in commands. They will understand whatever speech you may come up with. If required, could easily add speech commands to trigger the "ATTEND" & "GRD CALL" buttons to hear the chimes. In Prepar3D or FSX, when you hit button "GRND CALL", MCE will detect the event and simulate a "cockpit to ground" command so the mechanic replies within seconds without you saying anything.

You're welcome. Unable to replicate behavior with SOURCE and Control panel knobs. Total control with 737-700. I don't have other variants. Eventually contact support as we may need more info regarding the 900 and the right re-circulating fan The new set of speech commands are intended as such. To put the guard down (not lift it). Usefule to reset from a "failures scenario". And if you give the comman verbally (as opposed to testing it in Voxscript panel)), you'll be prompted to confirm you definitely want switching to happen. On the need to confirm topic, be aware, confirmation speech commands are dynamically enabled when a prompt is needed and disabled after the timeout for reply. Therefore, it may take half or up to a second for them to be ready to recognize following a prompt. Since they are very short, like "yes", "no", if this scheme wwasn't implemented, you would constantly have the mike randomly picking-up those short words. In general, when a switch is commanded to ON, OFF, Auto, override, if it has a guard switch it is automatically lifted, then if it's an override state that is requested, the guard switch stays up. If it's "set to normal", the guard is automatically set to closed. The eec switches have their own speech commands. There are tons of speech variations and only going to list 2. eec engine one set to alternate eec two switch to normal. With commands above, guards are handled automatically. The "guard switch eec one to closed" will just ensure the guard is put down.

Get the patch here Most items have been addressed. Download file, unzip and manually replace all files. Don't forget to replace "Availale_Commands.dat" for newly introduced speech commands. There are tons of speech commands for each item and only a few are listed.

Deliberately left out because potentially disruptive, with the risk FO accidentally shifting screens on final or takeoff. Could be secured of course as is the case for critical commands or only letting them through outside critical flight phases.. Maybe when there is nothing else to do, could be added. Guard controls already implemented. Patch will be ready by Friday.

In continuing to integrate as many complex planes as possible to provide a complete Multi Crew Experience (including mechanics, pursers, ramp agents), we are pleased to announce that the recently released Inibuilds A300-600 is now fully supported by MCE to same level as their A310. A virtual co-pilot that can set pretty much any switch or dial, to either conform to ANY airline SOPs or just have fun and call on the right seat guy to assist you when your hands are full. We won't turn you into a robot that needs to be aware about what the FO is programmed to do and try to fit in. YOU call the shots. Ask what you want, when you want and even using the speech verbiage you want if the tens of thousands of built-in speech commands don't spring to your mind naturally. Rehearse your own airline custom checklist or make do with the default provided one, up to you. See yourself with the fully working Demo available here. It supports many major complex planes in MSFS, Prepar3D or FSX. For instance, still only voice based product on the market where your FO can dial FCU SPD, HDG, ALT, VHF radios with Fenix A320. Not to mention, being able to assign the exact checklist you're used to if you happen to be a real world pilot. http://www.multicrewxp.com/Downloads.html

It's already pinned. I mean this thread. Because there are other pinned threads, the one that shows on top is the last one to which a post was added. The patches will always be prominent, among the first shown threads on first page.

Answers embedded in your post above.

That happens once every 12 hours or so and before MCE starts loading its stuff. So, it's not like an indication of something when it pops-up say only once a day.

Thanks for feedback. Never delete <Multi Crew Experience> folder found in \My documents\ folder as you would be getting rid of all default pre-made flows, not to mention any customization you may have done to them MCE interfaces the PMDG 737 ( and other PMDG planes) using their SDK. 75% of switches and dials can be read and set via the SDK. While there are commands to toggle guards in SDK, there is no way to read their current state via the SDK. You would need to make assumptions like "ok it's down, toggle once to lift it and then a second time to close it). But if the user manually messes with those guard switches it won't be reliable The reason it wasn't returning to normal is because the FO couldn't see the guard was lifted ( as he expected it to be so he can close it). There are a few vital other items that still aren't possible via the SDK like reading stab trim position so the FO can accurately position it when told "stabilizer trim five point 7 units". and that's where the module is used.

This one is no big deal, it's just a recommendation so that in the future they may get rid of some older Datarefs. For now, the plugin uses them as it supports XP-12, XP-11 & XP-10 According to the log, the plugin is definitely loading. The 32 Bit one doesn't and it's normal for a 64 Bit process not to load a 32 Bit plugin (doesn't see it as a valid file) which would only be loaded by XP-10 (32 Bit process). Try running X-Plane as administrator and starting MCE using simulator Plugins menu.

Make sure X-Plane is loading our "xpInsider.xpl" plugin The X-Plane log should say if it failed to load. Try starting X-Plane, then using its menu to start MCE. Menu Plugins->Multi Crew X-Plane->Start Multi Crew. If the menu is missing that entry, either the file itself is missing from \X-Plane\Resources\Plugins\ folder or something went wrong when the file was loaded. I assume you are using the latest patch and replaced all files that need to be.

You're welcome. I assume you manually replaced all files, including "mce.exe", "Simco64_Ldr.exe" and speech grammar files in \CandC\ folder In current implementation, as a reaction to "check flight data recorder" command he switches FDR to test, waits for 4 seconds, then puts it back on. No need for a separate command to bring it to normal. You can even set the guard and switch to random positions and he should be able to do the switching correctly.

You're welcome. Please get the patch here and manually replace a few files. You'll get the latest Patches - The Multi-Crew Experience (MCE) Support Forum - The AVSIM Community

If you're on Ultimate or MSFS edition, get the patch for your relevant edition here: Patches - The Multi-Crew Experience (MCE) Support Forum - The AVSIM Community Unless it's the PMDG 737 specific edition in which case you need to contact support. In latest V3.0.7.0 The spring loaded switch in picture above is now automatically set to OFF (middle) when FO checks the switch state. The flight data recorder switch can now be controlled via voice or a flow. Use any of these commands check flight data recorder test fdr data recorder check ...there are many more speech variations As for testable items on FO main front panel, here they are check annunciator lights check autopilot disengaged lights In general to request an item to be check you either start OR end the command with "check", "verify", "test", "please check", "please verify", "please test", "please have a look at test squibs verify overspeed warning stall warning check ....

We've had a few users in the past report issues with the Simbrief feature. In most cases it was because they altered C:\Users\ folder access rights which caused Windows not to allow MCE to write files to \My documents\ folder. Since very latest version, MCE will now create file in C drive under such scenarios. It is fixed in Ultimate and MSFS editions. A new patch has just been uploaded for the X-Plane edition. Obviously includes the fix. Download it and then confirm whether you still have the issue. Patches - The Multi-Crew Experience (MCE) Support Forum - The AVSIM Community

Answers embedded in your post.

First, welcome aboard. You're already advanced user. Will get back to you on various items gradually. I start with item 6 While this weird behavior was reported more than a year ago, it should have been fixed. Normally, no identical string should be added as MCE checks the content of the listbox first. But then you never know when non-English Windows setups are involved when string comparison doesn't yield the same result based on system locale. I assume you're on English Windows. For now, you could trim them as follows. Go to \My Documents\Multi Crew Experience\Myvoicescripts\Copilot\Aircraft\PMDG B737 MSFS\ Open each flow in Notepad (do not use fancy tools like Notepad++ or complex editors as they may introduce invisible characters or change the file format). You'll easily find the duplicates. Just get rid of them. You may want to read this thread as well New User Questions - The Multi-Crew Experience (MCE) Support Forum - The AVSIM Community

It would be silly to tie the key to devices that can disappear. I can assure you it's a well thought process that served us and our customers well for more than a decade. You won't even need a new key if you format C drive, install ANY Windows version. The same machine ID will be generated and putting back your saved key file will activate your copy.

OK will be looked at. If I'm not mistaken a long time ago we decided not to accept <ALT> key as it would trigger the main menu in Prepar3D or FSX. Maybe time to update Voxkey.

It's very likely your machine ID has changed. It won't run unless it finds a valid key for current machine ID. Not just any file with correct name. Fill-out "Registration.txt" file in MCE installation folder and send it to support.

If you mean "strobe lights" use commands "strobe lights on", "strobe light off" and they will be accurately switched (not just toggled) as FO will read the switch state first. If it's another light or the plane isn't fully supported yet, let me know which plane it is and explain which light we are talking about.

Sure, Regarding checklist... For items where the answer can be anything and the FO isn't expected to make sense of it, use one '_' (underscore) character. [ ] item in checklist -- _ MCE will then switch to "dictation mode" and you can say anything you want. Speech engine obviously may not pick-up exactly what you said as the dictation feature of the speech engine isn't as reliable as the "command and control" feature. For anti-ice or other checkable items that can be ON or OFF, use "as required" as the reply. [ ] engine anti-ice -- As required If you replay "as required", "as desired", FO will assume you intend the switches to remain in their current state. If you reply "ON" (or equivalent word) he will check it's ON. If you reply "OFF" (or equivalent word) he will check it's OFF. Regarding item 2. Since latest version, should be able to select 70 kts call-out on landing. Click button next to "Call-outs and monitoring" feature in "General" tab and you'll be able to customize call-outs. Grab the latest here Will get back to you regarding other items as soon as possible.

This is the link to the patch for the MCE Ultimate Edition This is the link to the patch for the MCE MSFS Edition (Do not use this for Airplane specific products like PMDG 737 edition or Fenix A320 edition)) V3.0.8.1 Minor bug fixes for things reported on this forum lately Begins FSS ERJ integration (still works in progress) V3.0.7.8 A few adjustments required to fit with latest PMDG updates to 737 (which caused a couple of switches not to be handled as expected) V3.0.7.6 Adds speech commands to ask mechanic to set/remove chocks Adds speech commands to control GRND CALL and ATTND CALL in a few aircraft (PMDG 737, Fenix A320, Flyywire) Fixed Recirculating fan switch not moving on command in PMDG 737 Tweaked the aircraft relocation via voice feature. V3.0.7.2 Adds speech commands for securing guard switches in PMDG 737 Adds new speech commands for controlling speed reference selector via voice Adds new spech commands for controlling n1 set selector via voice Adds voice control for stab trim override (aft pedestal switch) Fine tunes speech commands related to dialling SPD, HDG, ALT, MCP mode etc.. V3.0.7.0 Now fully supports recently release Inibuilds A300-600 to same level as Inibuilds A310. Adds voice control control for a few items in PMDG 737 V3.0.6.8 Improves ATR ECL checklist handling Patch requires MCE V3.0.6.0 or higher. This is the link for the patch MCE X-Plane edition Download, unzip and manually replace files as per folder structure. Sometimes, the links will be temporarily removed when a major update requires a full install.

Check you have xpInsider64.xpl and xpInsider.cfg files inside \X-Plane\Resources\Plugins\ folder. You may have more than one X-Plane installation and the installer only added the files to one of them. Normally it would prompt whether you have another installation (so it can copy the same files to the other setup), but it's easy to disregard the message. Also, don't forget <MCE dlls> folder which should be there as well \X-Plane\MCE dlls\