FS++

Rather than use the patch, install latet package (uploaded a few days ago) available from website. The version is higher tan what is shown on website. http://www.multicrewxp.com/Downloads.html

Affirmative. Un-install previous version via Windows Control panel. Do NOT delete anything maually, as your activation file and installed additional human recorded voice packs remain inplace. Simply download latest, unpack and run "InstallMCE". Should be all you need to do, except if you acquired Prepar3D V6 in which case you need to run tha app wizard briefly (no need for speech training) so that it edits "dll.xml" to tell V6 to load "fsInsider64.dll" on startup allowing MCE to connect to it. For V4 or V5, no need to do anything. Could you post the content of "Panel.cfg" for the Q400 Training edition?

Changes were made to ensure throttle lever position is always reported correctly by tapping into a separate variable. If one of them doesn't update in a timely manner, the other one will. I suggest you download the very latest V3.0.5.3 (website doesn't list the correct version). In addition to Fenix A320 fix, new package provides voice control for Asobo ATR. http://www.multicrewxp.com/Downloads.html

Update to latest and then report back. Ignore version displayed on website. It's actually V.3.0.5.3 http://www.multicrewxp.com/Downloads.html Demo always available from the link above. Is there anything peculiar with the FMC panels compared to the Pro version. I assume you made CDU 2 ready for clicking.

I doubt it's happening on the MCE side as those code sections (related to PF3) haven't been touched for a long while. maybe latest changes to "Simco64_Ldr.exe" is causing it. it's the app that simulates the actual key combo PF3 is expected to catch. I suggest the following... Install 3.20, then save "Simco64_Ldr.exe" somewhere. Install 3.52 (latest) and eventually replace "Simco64_Ldr.exe" with the older file. You'll lose Asobo ATR support in the process. FO will say he's doing things, but there would be no actions in the cockpit as that requires the updated file. http://www.multicrewxp.com/Downloads.html Thanks Report back. PS: Asobo ATR interfacing not complete yet. Flows not shipped, but will be within a few days.

Assuming V6 has the same folder structure as V5, and Since we don't perform any graphics operations inside the "prepar3D.exe" process, there is no reason whyt MCE wouldn't work with V6 the same way it does with the previous version. Nothing to loose by having a go at the Demo http://www.multicrewxp.com/Downloads.html The installer should add the following files and folders to \Prepar3D v6\ installation folder fsInsider64.dll fsInsider.ini A folder named <MCE dlls> with about 40 dlls inside it. No P3D files are modified inside the root folder. Assuming you ran the app wizard which will automatically edit "dll.xml" to add refrences to the "fsInsider64.dll" file, P3D should load it and MCE will be able to connect to the sim. From experience, the few things that occasionally break from one version to another, sometimes even between two patches are the following The spoken speech commands may not be displayed in Prepar3D. Integration with GSX needs to be tweaked a bit. Rarely, but may happen, the dll cannot workout the content of the ATC window. One way to check is to open the ATC window and ensure some options are available, then ask co-pilot "confirm ATC options". If the dll is able to work them out, should hear a voice spelling out those options. If not, some work will be required. We will be looking at V6 sometime next month and eventually sort out what needs to be. Don't forget, that same Demo can connect to MSFS, FSX, or even FS9

Grab latest patch Proceed as follows. Start Fenix A320 with ready for takeoff state. Set random values in FC for SPD, HDG, ALT and VS Start MCE, wait until things settle, then perform a quick takeoff and quit the sim. There should be a "Simco64_Ldr.log" in C:\Users\your_user_name\AppData\Roaming\Multi Crew Experience\ folder. The log should have a line displaying SPD, HDG, ALT and VS values. Make sure they are what the FCU was displaying when MCE started. It's not updated Should also see various lines showing throttle lever values. Mostly interested in the ones reported on takeoff. Those above 10000 No need to post the entire log. Just those lines.

Not sure, but could be caused by triggering copy protection system. As we don't discuss things here, I suggest you get in touch with support for help.

Sorry, not clear. APU control not working or the other stuff? Thanks

Sorry for the delay. More likely this week. More time needed to synchronize with electronic checklist. For instance, when you're first expected to read the <before takeoff checklist> the relevant header is at the top and it's a matter of validating the line, but once it's done it disappers and to get Fo to read it again, he has to play with a long list of options and screens before he can get to that specific section again.

It's being worked on. However, it seems Working Title hasn't yet finished what they set out to do. For instance FMC CDU page selection appears to only work on the left side unit and many line insertion not working even manually. Writing to scratchpad is working but LSK1, RSK2 etc for insertion don't seem to work using the dug up vars. It will be eventually worked out, as this stuff isn't well documented (no SDK yet). Also, behaviour seems to be slightly different when you have Asobo 787 only installed vs when you add "B78XH" to \Community\ folder. Which configuration are you on?

All you have to do is switch MCE ATC mode to "Other ATC" (as you would do with Pilot2ATC or Vatsim. Assign the same PTT joystick button you assigned in MCE for ATC in VoxAtc or other ATC and when you transmmit to ATC, Fo won't try to interpret your ATC speech. MCE doesn't interact with neither VoxATC nor Pilot2ATC, this means you could have the Fo occasionally speak wat MCE tells it to but also what the other program wants him to say.

Sorry about that. It can happen when users mistakenly use the patch available on forum. That one is for Ultimate Edition only. Since it's a different product, the activation file for say MSFS edition or other products won't work, with silent stall on startup. The MSFS edition will be updated to V3.0.4.8 or higher this week. It will add GSX integration as well as full support for Asobo ATR and Asobo 787 Working Title mod.

Get this patch Manually replace 2 files inside MCE installation folder. Anyone on older Ultimate Edition version than V3.0.4.1, you need to install the latest package first http://www.multicrewxp.com/Downloads.html Those on aircraft specific packages, please wait for your relevant package to be updated later this month. Regarding Fenix A320... Please don't start asking Fo to perform things until you have seen the "arm salute" (raising and lowering of his seat left arm), indicating he has worked out all the variables he needs to monitor. This happens approximately 30 to 45 seconds after the MCE UI is showing.

FO looks for keywords like "flap" or "flaps", "cowl" etc to identify item. Considering you're using TTS voices which can utter anything, a workaround would be to type "flaap" or "flaaps". FO will then see it as unhandled item and will accept any answer. As for PMDG 737, only have the 700 variant. It's possible the transponder equipment on other variants isn't the same, hence Fo possibly mishandling the switch. Could you post a picture of the actual transponder panel on your plane? Thanks

As part of the reply, try using keyword "check" or "verify" in which case you may reply with anything and he won't challenge you on that [ ] item referring to flaps -- check _ EDIT: Forgot to mention... GSX integration is only in Ultimate and MSFS editions. If using the PMDG 737 or any other aircraft specific product, it will come in next update sometime this month.

It should work. When MCE detects GSX is running, it automatically switches to that mode (as opposed to using native ground services). There may be some planes where it doesn't. Please report. Notably, to handle service doors automatically on GSX request, some custom interfacing must be done. With so so many planes to cover.. (never mind those that aren't accounted for yet). Refueling request and menu selection will always work. As some planes use custom refuelling via CDU what happens after the request can be a hit and miss. Changelog: Adjustments made to ensure it works on non-English Windows Editions as expected. Now supports WorkingTitle mod to Asobo 787. Still works in progress.

Latest V3.0.4.7 has significant integration with WT mod to Asobo 787. A couple more weeks and it should be sorted. http://www.multicrewxp.com/Downloads.html

You're right, not only undocumented, but it's not even there in the default mce.ini Thanks for reporting this. Look at this section [RAMP] NoRampToOfficeTalk=0 NoPaxDoorsAutoHandling=0 NoCargoDoorsAutoHandling=0 Add the following line.... NoGreeting=1 Will get back to you regarding the other unusual flaps consideration

With regards Ramp services.... Documentation is available via the Windows menu. Start->Multi Crew Experience_you will see many docs. You'll find the commands not listed in "Available_Commands.dat" there. Refer to "GSX&AES pdf doc for speech commands to use. In general all commands addressed to rampy must start with either the name of the ramp agen or "ramp agent", "despatch", "ramp coordinator". Eventually, if you can't be bothered to remember the many built-in commands, make your own. See how in this thread. Regarding checklist... If the reply always starts with the same word, you'd be better off writing "that_word(s)" followed by an underscore. [ ] Checklist item -- familiarWord _ That should help the speech engine differentiate between those replies and the specific commands to dial VHF, NAV freqs

Congrats on your promotion. Sometimes I write things intended for others who may stumble across the thread by accident. You, me and many following this forum closely know and understand we have the technical edge and provide the deepest and most flexible integration with the most prominent planes on the market. . Too many who still think that a product that supports 50 complex planes across all Microsoft and Lockheed Martin simulators must be generic in nature. How is that possible...Well, 15+ years of full time development and counting.🙂

Thanks for the offer. I do have own Fenix A320 copy, so it's not like trying to implement a "generic solution" that relies solely on feedback. And I'm not in this alone either. Collegue Ben does the heavy lifting. Now that you have checked your throttle and confirmed it is happening despite levers being higher that CLB, it's a matter of revisiting the plane in the context of the latest version it's in and working it out. For instance, FO determines the flight phase based on many parammeters, among them throttle levers positions. In an ideal world, all MSFS planes would use default MSFS vars for throttles, the positive range being from 0 to 16383 and the Climb position at same value (somewhere above 11000. Unfortunately it's not the case. Some planes use default variable, other rely on a custom one (and own range). Some start with default, then in airplane update move to using their own var. The reference value can vary from 9000 to 12000 when you include de-rated power setting on some planes (and that is just a guess). Each plane update has the potential to break the interfacing. You're never completely done. Take reading CDU Vspeeds for instance or FCU, SPD< HDG, ALT panel as well as FMA state. No wonder no other voice control product on the market bothers to implement that. It's way too hard. There is no SDK for this. It requires complex workarounds which may need adapting and maintenance as the plane gets updated. Feedback is important because we can't spend our time flying for 2 hours on each fully supported plane, every time the software gets updated just to spot something that may happen on approach or something. We do spend it on interfacing more and more planes (withpout charging a dime) so you can get "Install once, fly many to extreme detail). The customers are more likely to find the little imperfections. Therefore do not hesitate to report as you did here. The plane will be looked at this within the next 2 days.

Get this file Unzip and replace fsInsider64.dll inside \Prepar3D v5\ (as well as \Prepar3D v4\) installation folder.

Answers embedded.

Welcome aboard goose_lives69 The UI should only auto-minimize when in these screen panels, General, Command, Checklist, ATC, Sim, and About. It should remain put when editing the flows. Regarding checklist... Only a single underscore "_" is allowed per line. You can speak anything you want there and FO won't challenge you For items that the human recorded voices weren't prepared to handle like "PWB", write it as "P W B". You can have a line checked by Fo only and move to next by adding this marker at the end of the checklist Line [ ] flaps -- Set //2 If both you and the Fo are expected to reply, use //3 With no marker, by default you are expected to reply. The flows aren't set in stone, nor are they realistic by default. Think of them as a list of actions you expect Fo to perform. You can add more, remove some until the task sharing is ideal for your airline. You can add these commands to any flow... check gpws gpws test test gpws verify gpws check transponder test transponder transponder test verify transponder. Now, if you wanted to be able to say "GPWS SYS Test" (which isn't a built-in command), I refer you to this thread where you can learn how to "eductae" your Fo to understand ANY speech you want to come up with.