Is it just me?  Or has anyone else using the PMDG 737 in the 2024 beta had the web FMC suddenly go haywire?

I know I can’t expect things to work properly in the beta.  But I’ve been flying the 737 just fine in both the SU1 and SU2 betas.  Granted, there are a couple of quirks, but it’ll do fine until it’s officially supported, which could be quite awhile yet.

But with the latest beta build, suddenly the web FMC no longer works properly.  The display is erratic and after trying to use it I get a CTD.  Happens every time.  I can fly the 737 normally as long as I don’t try to access the web FMC. 

I normally use it on my iPad, and it’s wonderful.  I checked in MSFS 2020, and it still works fine there, as does the 777 FMC in the SU2 beta. 

So I’m curious if it’s just me, in which case I’ll do some more troubleshooting and investigating, or are others seeing  the same?

 

PMDG 737 is still MSFS2020 only

Officially, that's true of course, which I acknowledged.  I'm not looking for support.  Just perhaps some feedback from any other beta users who may or may not have seen a similar issue with the web FMC. 

My understanding is that WebFMC won't work with 2024.

2 hours ago, 301ad said:

Just perhaps some feedback from any other beta users who may or may not have seen a similar issue with the web FMC. 

I will try that tonight. Generally speaking, if the FMC screen is displayed correctly depends on how well PMDG's SDK is sending the data (or at all). So it comes down to general compatibility between SU2 SimConnect and the version that the PMDG SDK has been written for. In general I wouldn't expect any trouble, but you just never know. Remember to keep an eye on the PMDG Options.ini file, it may be invalidated when a new sim update drops.

I have a new variant of those WebFMCs too, which will now work for all aircraft where you can pop-out the FMC screen. The tech is no longer limited to aircraft that have an SDK or HTML screens, and it works with for example the Fenix and the iniBuilds aircraft. Release is planned together with AAO 4.53 - and I guess that I should wait until SU2 is complete as well... Any AAO user who is interested in trying this, send an email with your proof of purchase to the support address (last page of the AAO manual). Be aware though that the new WebFMC can only work when the pop-out mechanism in general is working for you - that is not the case for everybody.

Edited April 17, 20251 yr by Lorby_SI

4 hours ago, 301ad said:

Just perhaps some feedback from any other beta users who may or may not have seen a similar issue with the web FMC. 

Tested just now, PMDG 737 in MSFS2024. The FMC screen is only updated once, and after three clicks the simulator CTDs. And that is in AAO 4.53, my current development version, which already has the latest SimConnect libraries that were released with the Beta SDK.

Edited April 17, 20251 yr by Lorby_SI

Thanks for checking.  That's pretty much what I've been seeing, using 4.52 b39.  It had been working fine in the SU2 beta up to 1.4.12.0.  This trouble started for me with 1.4.13.0.

So I did a little experimenting, opting out of the beta and back to 1.3.23.0.  In this version at first it still wasn't working, but then I deleted the template I was using for the 737, started a new one, activated the aircraft automated scripts, and after a couple restarts of AAO and the sim, surprise surprise it's working again.  Starting a flight, I'll let you know how it goes.  Then I'm going to go back to the beta build and see what happens.

11 minutes ago, 301ad said:

Thanks for checking.  That's pretty much what I've been seeing, using 4.52 b39.  It had been working fine in the SU2 beta up to 1.4.12.0.  This trouble started for me with 1.4.13.0.

So I did a little experimenting, opting out of the beta and back to 1.3.23.0.  In this version at first it still wasn't working, but then I deleted the template I was using for the 737, started a new one, activated the aircraft automated scripts, and after a couple restarts of AAO and the sim, surprise surprise it's working again.  Starting a flight, I'll let you know how it goes.  Then I'm going to go back to the beta build and see what happens.

The whole affair really isn't that mysterious. When you activate the PMDG SDK, the plane writes the contents of the screen into a SimConnect data object. Every client that wishes to do so can read it and extract the data. This data area is supposed to notify the client when the contents change - that is how it has been working since forever. At the moment that mechanism doesn't work for PMDG. Either they are inable to write to the data area all the time, or the notification doesn't work. 
SimConnect data areas in general work fine in this MSFS 2024 version - AAO uses one too for other purposes, and there is no trouble with that one at all. As far as I can tell this issue is currently only with PMDG, and the worst bit is the CTD after you press a few buttons on the FMC. They will have to update their middleware I guess.

As I wrote above, the next generation of my WebFMCs doesn't need this functionality anyway, so I don't think that it is worth investing any effort into this. Just wait until PMDG releases a 24 compatible version, then we'll see.

Edited April 17, 20251 yr by Lorby_SI

OK, not great, the WebFMC stopped updating its screen pretty quickly and led to a total freeze up.  I didn't get far in the flight planning before this happened.

So, I don't know what happened, but it was working fine before and now it isn't.

 

45 minutes ago, 301ad said:

So, I don't know what happened, but it was working fine before and now it isn't.

For me it is still working fine - in MSFS 2020.

Maybe make the 737 recompile its WASM modules? For that, delete the compiled package here:
AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\pmdg-aircraft-737
Be mindful that this is also where the 737_Options.ini is. After the recompile you have to add the SDK lines to that file again.

After deleting the build folder, start the sim, load the plane, wait until you are sitting in the cockpit. Then shut down the sim again, alter the Options.ini and restart the sim. Now everything should be "fresh" again.

Edited April 17, 20251 yr by Lorby_SI

On 4/17/2025 at 6:55 PM, Lorby_SI said:

As I wrote above, the next generation of my WebFMCs doesn't need this functionality anyway, so I don't think that it is worth investing any effort into this. Just wait until PMDG releases a 24 compatible version, then we'll see.

Hi, just reading about the new tech making me a bit worried, will you still release html based webfmc whenever possible ? Because I don’t like the popout window function of MSFS and if the new tech is based on that I would say it’s a downgrade, because with popout windows my msfs is noticeable more unstable and framrate also gets a hit when using. So for me the „old“ webfmc are godsend and working amazing fast and stable. 
for airplanes that doesn’t support the old way they are ok but please don’t make all airplanes only with the new webfmc tech.

3 minutes ago, Bam2000 said:

but please don’t make all airplanes only with the new webfmc tech

There are three types of WebFMCs:

1. Native developer SDK (PMDG, Leonardo, iFly, CRJ, MD11)

2. Popout + AAO web page or WebFIP ( that's the new tech and the only way to grab WASM based CDUs )

3. Streaming the contents of the CDU from inside the sim - only possible with HTML instruments - not many of those left.

Option 3 is in most cases no longer working in MSFS 2024 because of the locked VFS and because many developers seem to prefer WASM. That's why 2. is currently the way forward.

Option 2. has drawbacks, no doubt. Popouts don't work for everybody, some graphics settings apparently make the sim freeze when you pop out an instrument. But I don't see any alternative.

So I did "refresh" my whole 2024 installation and all seems to be working well again, including the previously troublesome webFMC in the PMDG 737s.

I first opted out of the beta, then decided to go even further and delete the whole thing and reinstall. 2024 is pretty good with that, it's only about a 9GB download.  I also decided to just install the sim into its default location, while still keeping the Community folder on a separate drive.  (Previously I had used a custom location for the sim install.) Then I copied over the 737 and 777 from 2020, as per the user guidance on the PMDG Discord.  Checked that everything seemed to be working, and then I opted back into the beta.  Again, all now seems fine after a number of 737 flights.  So, I don't know what caused it to go haywire for me.  Maybe the suggestion to recompile the WASM modules would have been enough to get me back on track.  But I'm good now, and we'll see if it lasts.

I hope it does, as I agree with Bam2000.  I tried the Popout version (thanks Oliver!) and although it did work I do prefer the original native PMDG version.  Fenix also has their own MCDU version which is very good.  Hopefully we won't lose these going forward.

The webFMC is working for me in 2024 using the PMDG 777-200ER, however it only works locally, even when using an IP instead of "localhost". It won't connect to the webapi if I use a tablet or phone.

11 minutes ago, mrm0508 said:

The webFMC is working for me in 2024 using the PMDG 777-200ER, however it only works locally, even when using an IP instead of "localhost". It won't connect to the webapi if I use a tablet or phone.

That is usually a Firewall issue.