12 minutes ago, FS++ said:

Will post the download link tonight UK time.

Thank you ☺️ 

On 5/17/2025 at 4:10 PM, Balint Szarka said:

Thank you ☺️ 

You're welcome.

Download from this link

 

Edited May 29, 20251 yr by FS++

On 5/11/2025 at 8:50 AM, FS++ said:

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.

 

Gerald, honestly, I have not done anything regarding this.  I needed to re-learn how to fly the 777 so I've just been doing everything solo.  I also thought I'd let things settle down.  SU2 just became official and Randazzo said Asobo changed the SDK so PMDG had to make changes to the 777F coming out and the -200ER.  That should be Monday, so I'll take a look at it after that.

I can confirm that there are two 777_Options.ini files on my computer.  One is in the MSFS 2020 appdata folder path that you described.  The other was in the WASM folder path for MSFS2024 that I posted earlier.  The only thing under the work folder you suggested for MSFS 2024 was a community folder and within that an asfs folder.  That is all.

OK, I tried again with the same results.  Nothing really works...I could say "set flaps 5" and that would work, but "set flaps 1" I got the response that it was already there.  Same with "flaps up".  Like you said, it seems that MCE doesn't know where anything is set which is why the first command worked but the subsequent commands don't.

I opened a ticket with PMDG and very specifically asked if the SDK worked for "read" and "set" like the -300ER, and I explained what I was trying to do using multi-crew experience.  This is the response I got:

"Hello Donald

 

Any changes would have been distributed with the 200ER on release.  My suspicion is the issue is actually related to the SU2 update as that seems to have broken some functionality in that area."

 

I just don't remember exactly when I tried MCE relative to the SU2 beta release, so I can't say for sure if I tried it on SU1.  I jumped back and forth with SU2 beta.

On 5/6/2025 at 1:31 PM, FS++ 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.

 

 

Mine is located in C:\Users\Cory\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-77er\work

I edited the SDK lines in accordingly, then started FS and MCE as usual with no luck, so far. Same behavior.

On 5/20/2025 at 2:09 AM, crab said:

Mine is located in C:\Users\Cory\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-77er\work

I edited the SDK lines in accordingly, then started FS and MCE as usual with no luck, so far. Same behavior.

If you have the 300ER, check it out with SDK enabled and you'll see it works as expected.

There is a possibility PMDG has not yet internally enabled the "data broadcast" side of the SDK on the new plane. Option enabled in ini file won't matter

They did that even with the 737 after initial release where it was enabled, then disabled it in some update, only to be restored some time later.

Ask on their forum whether the SDK is confirmed as fully working and not just taking simulated clicks (that part has always ben enabled).

The same SDK should cover all plane variants, including the Freighter.

4 hours ago, FS++ said:

If you have the 300ER, check it out with SDK enabled and you'll see it works as expected.

There is a possibility PMDG has not yet internally enabled the "data broadcast" side of the SDK on the new plane. Option enabled in ini file won't matter

They did that even with the 737 after initial release where it was enabled, then disabled it in some update, only to be restored some time later.

Ask on their forum whether the SDK is confirmed as fully working and not just taking simulated clicks (that part has always ben enabled).

The same SDK should cover all plane variants, including the Freighter.

I have the 300ER but it is not released in 2024 yet. Works great in 2020. I tried it in all 777 variants in 2020 and MCE works great. Tried it in the freighter in 2024 and it did not work, even after adding the SDK lines in the applicable 777_options.ini and restarting everything, same as the 772ER in 2024.

I've done the SDK dance every PMDG release, so adding it was the first thing I tried. And I do remember the releases where it was disabled for a bit, so writing PMDG is my next step.

But, I see here another mod requiring the SDK seems to work. 

FYI, I just loaded up the Cessna Longitude in MSFS 2024 and it was the same behavior as the -200ER.  Some commands would work in one direction, but not the other.  A lot of commands just didn't work at all.  

Got a reply from PMDG...

Quote

The settings have effect. I am using them on my setup in order to communicate with other programs externally with no issue.

 

Chris Makris
Customer & Product Support
PMDG Simulations, LLC
www.pmdg.com

 

 

17 hours ago, FlyData said:

FYI, I just loaded up the Cessna Longitude in MSFS 2024 and it was the same behavior as the -200ER.  Some commands would work in one direction, but not the other.  A lot of commands just didn't work at all.  

This is probably a different issue.

While it's possible to install MCE anywhere, you would need to run MSFS as administrator and disable Windows UAC. That's why we recommend to install to default path where "mce.exe" has all the rights it needs to interact with other executables. Only takes 2 GB max, including after installing all the 10 human recorded co-pilot voice packs.

Which MCE version number are you on?

Edited May 22, 20251 yr by FS++

1 hour ago, crab said:

Got a reply from PMDG...

 

Thanks for the follow-up.

I'm not sure what kind of usage he's referring to.

The events sending side of the SDK always works even without that option enabled.

For hardware sim-pits that could be enough. It's not like if taxi light goes off in the sim VC, it would force the hardware switch to go off. All the operator needs is for the toggle to work in VC while visually checking it.

The "EnableDataBroadcast=1" is what causes the plane to report in which state select items are.

One can get away with the issue if the crew simulation was completely scripted. Like "start from cold and dark", don't touch what the FO is handling, then make assumptions with regards which state the target switch is and toggle it with the assumption it will go into a specific state etc...

MCE is designed from the ground up for speech recognition, with no assumption as to what you would want the Fo to perform next, and you are expected to touch those switches yourself as well. Therefore accurate control requires checking the state before eventually toggling, or not.

If you don't mind, try creating a new folder as per the usual location and copy the "777_options.ini" to it.

C:\Users\Cory\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\Packages\pmdg-aircraft-77er\work

Eventually, delete everything in the copied file except for these 2 lines

[SDK]

EnableDataBroadcast=1

Restart MSFS.

Thank you

 

Negative, no change.

https://imgur.com/a/7BDRU5t

On 5/22/2025 at 8:15 PM, crab said:

Negative, no change.

https://imgur.com/a/7BDRU5t

Next week, we'll have a new "Simco64_Ldr.exe" that will read stuff from the sim using Asobo SDK as opposed to PMDG SDK. A stop gap until PMDG SDK is fully enabled. We don't think it is right now for the 200ER. Setting has no effect.

 

Edited May 24, 20251 yr by FS++

Hi Gerald. Any news on this?

New MCE version is online and works with the latest release of 777 from PMDG for MSFS2024. A great compliment to the developers.

Edited June 6, 20251 yr by Cargostorm