9 hours ago, fredo340 said:

Hi,

 

Would be nice to have the Inibuild A350 supported. Thanks

 

I second this too. 

I also wonder would it be possible to have a file created within MCE’s folder that would make it to be recognized even if that means the FO won’t be able to do much in the cockpit? You could be asking why would I want that? Well I have written quite a lot of lua files that are ran by MCE which in turn does complex stuff and complements the FO. So understand it in a way that MCE provides the voice recognition and limited aircraft knowledge and the lua files do checks on systems and complex stuff. The two together is a dream come true.

On 5/1/2025 at 9:16 PM, Balint Szarka said:

I also wonder would it be possible to have a file created within MCE’s folder that would make it to be recognized even if that means the FO won’t be able to do much in the cockpit? You could be asking why would I want that? Well I have written quite a lot of lua files that are ran by MCE which in turn does complex stuff and complements the FO. So understand it in a way that MCE provides the voice recognition and limited aircraft knowledge and the lua files do checks on systems and complex stuff. The two together is a dream come true.

I assume those Lua scripts are handled by FSUIPC when a key combination is pressed.

If that's the case, it's just a matter of creating custom commands in Voxkey, (Not Voxscript) to trigger them 

Windows menu Start->Multi Crew Experience->Voxkey.

For MSFS, open "FS2020.vkp" profile and create your custom commands in it.

When MCE runs, it looks up the profile for the running sim (FS2020.vkp" covers both MSFS 2024 & 2020) and makes your new speech commands available which when recognized, will get MCE to send the relevant key combo to MSFS.

 

 

2 hours ago, FS++ said:

I assume those Lua scripts are handled by FSUIPC when a key combination is pressed.

If that's the case, it's just a matter of creating custom commands in Voxkey, (Not Voxscript) to trigger them 

Windows menu Start->Multi Crew Experience->Voxkey.

For MSFS, open "FS2020.vkp" profile and create your custom commands in it.

When MCE runs, it looks up the profile for the running sim (FS2020.vkp" covers both MSFS 2024 & 2020) and makes your new speech commands available which when recognized, will get MCE to send the relevant key combo to MSFS.

 

 

That’s correct. They are ran by FSUIPC and I have used Voxkey and entered key combinations to trigger the individual.lua files.
My problem is that I am doing this on unsupported aircraft like the A350 and the MD11 - which means that MCE needs the Voxscript files all in the Other ASOBO jet aircraft (or whatever is called) folder. And once you do this to more than one plane it can get a bit confusing on which command was which aircraft. You see I am using Voxkey to insert keyboard shortcuts and instead of writing understandable commands I just abbreviate them so it does not get recognised by the voice recognition and then I insert those abbreviated commands in the Voxscript files. So you can see it can get very crowded in one folder. It would be nice if planes that are unsupported can get their own folder based on their aircraft.cfg (categorised by model maybe?).

Hello, I just got the PMDG 777-200ER for MSFS 2024.   MCE connects to the plane and the co-pilot boards, then I tried importing the scripts I wrote for the 777-300ER in MSFS 2020.  When I run the scripts the co-pilot announces he is starting, but nothing happens in the plane.  I was hoping it was similar enough to be able to port over, but maybe not.  Should it work?  Or is an update needed?  Thank you.   

--Don

2 hours ago, FlyData said:

Hello, I just got the PMDG 777-200ER for MSFS 2024.   MCE connects to the plane and the co-pilot boards, then I tried importing the scripts I wrote for the 777-300ER in MSFS 2020.  When I run the scripts the co-pilot announces he is starting, but nothing happens in the plane.  I was hoping it was similar enough to be able to port over, but maybe not.  Should it work?  Or is an update needed?  Thank you.   

--Don

Because MCE interfaces PMDG planes using their SDK, a specific text entry needs to be added to a specific PMDG file related to the last plane you acquired that wasn't there when you installed MCE.

Just un-install and re-install MCE and the SDK for that variant will be enabled. After that co-pilot will be able to control and read state of pretty much any dial or control.

Typically, this is added....or edited

[SDK]

EnableDataBroadcast=1

Unlike with FSX & Prepar3D where PMDG would have a single file for the aircraft type, in MSFS, each variant has its own file, 737-700, 737-800, 777-300, 777-200 etc..

17 hours ago, Balint Szarka said:

That’s correct. They are ran by FSUIPC and I have used Voxkey and entered key combinations to trigger the individual.lua files.
My problem is that I am doing this on unsupported aircraft like the A350 and the MD11 - which means that MCE needs the Voxscript files all in the Other ASOBO jet aircraft (or whatever is called) folder. And once you do this to more than one plane it can get a bit confusing on which command was which aircraft. You see I am using Voxkey to insert keyboard shortcuts and instead of writing understandable commands I just abbreviate them so it does not get recognised by the voice recognition and then I insert those abbreviated commands in the Voxscript files. So you can see it can get very crowded in one folder. It would be nice if planes that are unsupported can get their own folder based on their aircraft.cfg (categorised by model maybe?).

Up to Prepar3D, MCE used to create a separate folder for each plane variant based on the "sim=whatever_text_is_there" (in aircraft.cfg under [fltsim.X] section) which also corresponded to the name of the folder that held the aircraft files.

Unfortunately, this is no longer possible or reliable. Starting from MSFS, MCE needs to know the plane ahead of time in order to identify it and make the relevant folder for it, not to mention whare the Fo is expected to find the flows.

The good news, Inibuilds A350 integration is already works in progress since beginning of April and nearing completion.

In next update, we'll make provision for the TFDi MD11 to have its own <MD11> folder.

Voxkey should still work though. The catch is that buillt-in speech commands always take precedence over custom ones. And if there are flows in the folder, their names become built-in commands. So if you say "before start flow" and you happen to have a flow with that name, it's the built-in command that will trigger, not your other "before start flow" that is expected to trigger the Lua script via key combination.

The solution is to add commands that don't exist to Voxkey profile like....

"configure the plane for before start" or "set me up for start"

"configure the plane for taxi" or "set me up for taxi"

"configure the plane for climb"

Since there are no built-in commands among the tens of thousands built in that start with "configure", I anticipate, the speech engine will pick them up easily and reliably, especially, the worded ones.

By the end of this week, you could request the download link for the Beta package that already supports Inibuilds A350.

I still can't get this to work in MSFS 2024 with the 777-200ER.  I reinstalled as you said and I can connect to the plane.  It shows at the top that it is the 777-200ER GE variant.  But when I ask the co-pilot to perform a task, he repeats it back to me but it just doesn't happen in the cockpit.  Do you know where the EnableDataBroadcast=1 needs to go?  I can't find any reference to an SDK in the installation files.  Thanks.

10 hours ago, FlyData said:

I still can't get this to work in MSFS 2024 with the 777-200ER.  I reinstalled as you said and I can connect to the plane.  It shows at the top that it is the 777-200ER GE variant.  But when I ask the co-pilot to perform a task, he repeats it back to me but it just doesn't happen in the cockpit.  Do you know where the EnableDataBroadcast=1 needs to go?  I can't find any reference to an SDK in the installation files.  Thanks.

The installer is only prepared to handle 3 possible PMDG aircraft folder names so far.

 “pmdg-aircraft-77w”  “pmdg-aircraft-772” and “pmdg-aircraft-77F”

 The newly released PMDG 777-200ER probably has a different name.

 For MSFS 2024 Steam Edition, the location of “777_Options.ini”, the file that requires editing to enable SDK, would be under

 “C:\Users\Your_user_name\AppData\Roaming\Microsoft Flight Simulator 2024\Packages\whatever_Pmdg_777_aircraft_folder_name\work”

  

For MSFS 2024 Market place Edition

 “C:\Users\Your_user_name\AppData\Roaming\Packages\\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\Packages\whatever_Pmdg_777_aircraft_folder_name\work”

 Open “777_Options.ini” on that specific path, using Microsoft Notepad and ensure…

  [SDK]

EnableDataBroadcast=1

 Re-start MSFS 2024 so that the plane enables its SDK, wait until the aircraft has finished loading. Only then, start MCE.

OK, I found the 777_Options.ini file for the -200ER and modified accordingly.  FYI, it was in a different path (steam version):

C:\Users\Username\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\pmdg-aircraft-77er\work

I got MCE to connect, but only some commands work.  Overhead panel lights don't work, but I said "flaps 5" and that worked.  "Flight director on" also worked.  Set altitude and set heading moved the dial, but not to where I said.  autobrake didn't move, spoilers didn't either.  I'm just using single commands and not trying any voxscripts.    Thanks.  I won't post  here anymore as I know this is the new planes thread and not a problem solving thread.

3 hours ago, FlyData said:

Set altitude and set heading moved the dial, but not to where I said

The FO will typically read the current MCP value, then increment/decrement relative to that value.

If he's adding 150 knots after you say "set speed 150", chances are this is caused by the SDK not broadcasting data as it should. He's reading zero speed on MCP every time

This is known to have happened with other planes like their 737.

They sometimes disable the SDK for initial release because it has some cost, constantly broadcasting the sate of dials and switches states, and adding "EnableDataBroadcast=1" would have no effect.

I'm really surprised the options file is under Microsoft Flight Simulator 2024\WASM\

Can you double-check whether there is a 

C:\Users\Your_user_name\AppData\Roaming\Microsoft Flight Simulator 2024\Packages\pmdg-aircraft-77er\work folder?

It's the 777_Options.ini file inside that folder that would typically enable-disable the SDK.

I suggest you read the manual to find out which exact file needs to be edited and eventually visit PMDG forum to see if the SDK has been confirmed  working.

There is a way to quickly check all the available commands, without looking up the manual.

In MCE UI, go to "Command" tab and click <Voxscript>

Select any flow and click <Edit>

In next screen, click <Edit script command>

In "Script commands" panel, click <Command> button.

You should see a listbox containing all sorts of speech commands to handle pretty much anything.

Insert a command, then either speak it or use the <Test> button to see the FO execute it.

Dialing commands aren't listed because they cannot be scripted.

 

 

On 5/5/2025 at 5:49 PM, FS++ said:

Up to Prepar3D, MCE used to create a separate folder for each plane variant based on the "sim=whatever_text_is_there" (in aircraft.cfg under [fltsim.X] section) which also corresponded to the name of the folder that held the aircraft files.

Unfortunately, this is no longer possible or reliable. Starting from MSFS, MCE needs to know the plane ahead of time in order to identify it and make the relevant folder for it, not to mention whare the Fo is expected to find the flows.

The good news, Inibuilds A350 integration is already works in progress since beginning of April and nearing completion.

In next update, we'll make provision for the TFDi MD11 to have its own <MD11> folder.

Voxkey should still work though. The catch is that buillt-in speech commands always take precedence over custom ones. And if there are flows in the folder, their names become built-in commands. So if you say "before start flow" and you happen to have a flow with that name, it's the built-in command that will trigger, not your other "before start flow" that is expected to trigger the Lua script via key combination.

The solution is to add commands that don't exist to Voxkey profile like....

"configure the plane for before start" or "set me up for start"

"configure the plane for taxi" or "set me up for taxi"

"configure the plane for climb"

Since there are no built-in commands among the tens of thousands built in that start with "configure", I anticipate, the speech engine will pick them up easily and reliably, especially, the worded ones.

By the end of this week, you could request the download link for the Beta package that already supports Inibuilds A350.

Lovely. I am looking forward to the 350 implementation. At least after the 350 is added then I can remove the Voxscript files and will be only the MD11, until that comes out too. Thank you ☺️ 

On 5/5/2025 at 2:57 PM, FlyData said:

Hello, I just got the PMDG 777-200ER for MSFS 2024.   MCE connects to the plane and the co-pilot boards, then I tried importing the scripts I wrote for the 777-300ER in MSFS 2020.  When I run the scripts the co-pilot announces he is starting, but nothing happens in the plane.  I was hoping it was similar enough to be able to port over, but maybe not.  Should it work?  Or is an update needed?  Thank you.   

--Don

What's the situation regarding this? Are they confirming that the SDK works for both "read" and "set" in the 200ER just as it did with the 300ER?

Toggling items should work. Otherwise Fo wouldn't even be able to set the flaps.

You can't have accurate control unless Fo is able to read the state of Dials and controls before acting on them (that's what EnableDataBroadcast is related to).

If required, could send you a replacement file that would read MCP, SPD, HDG, ALT directly from the sim using Microsoft SDK.

 

Edited May 11, 20251 yr by FS++

On 5/5/2025 at 5:49 PM, FS++ said:

Up to Prepar3D, MCE used to create a separate folder for each plane variant based on the "sim=whatever_text_is_there" (in aircraft.cfg under [fltsim.X] section) which also corresponded to the name of the folder that held the aircraft files.

Unfortunately, this is no longer possible or reliable. Starting from MSFS, MCE needs to know the plane ahead of time in order to identify it and make the relevant folder for it, not to mention whare the Fo is expected to find the flows.

The good news, Inibuilds A350 integration is already works in progress since beginning of April and nearing completion.

In next update, we'll make provision for the TFDi MD11 to have its own <MD11> folder.

Voxkey should still work though. The catch is that buillt-in speech commands always take precedence over custom ones. And if there are flows in the folder, their names become built-in commands. So if you say "before start flow" and you happen to have a flow with that name, it's the built-in command that will trigger, not your other "before start flow" that is expected to trigger the Lua script via key combination.

The solution is to add commands that don't exist to Voxkey profile like....

"configure the plane for before start" or "set me up for start"

"configure the plane for taxi" or "set me up for taxi"

"configure the plane for climb"

Since there are no built-in commands among the tens of thousands built in that start with "configure", I anticipate, the speech engine will pick them up easily and reliably, especially, the worded ones.

By the end of this week, you could request the download link for the Beta package that already supports Inibuilds A350.

Dear developer,

I am wondering whether the beta package you mentioned would be available that supports the iniBuilds A350?

Kind regards,
Balint

On 5/15/2025 at 9:58 PM, Balint Szarka said:

Dear developer,

I am wondering whether the beta package you mentioned would be available that supports the iniBuilds A350?

Kind regards,
Balint

Will post the download link tonight UK time.