301ad

You, sir, are amazing. I changed "zzz_*" to "aaa_* and the 787 webFMC now seems to be working fine. I'm just sitting at a gate, haven't tried a full flight yet, but will report back if it goes south again. Thanks so much, again, for your amazing support.

I can report that the webFMC works just fine on my iPad in 2024 SU2 using the new 777-200ER. (Also using the as yet unsupported 777-300ER and 737 series.) As another data point, I haven’t had any luck with is the Horizon 787-9 mod in 2024. I see the keys and they do affect the FMC in the sim, but there is no display screen.

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.

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.

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.

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.

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?

Just happened to me, too. I noticed my baro setting was at 28.85. Must have been because my previous flight had ended at EGLL, where the pressure was that low. I reloaded the weather in Opus, and the baro reading was 30.15. The doors were then able to operate normally. Alan Davies

Update: It turns out that the cure for me was to change UPPER_FRAMERATE_LIMIT from 30 to 0. No more freezes for me. It may or not work for anyone else.

Unfortunately, although it seems to have helped some people, disabling autosave did not stop my freezes.

Also, I've noticed that the 777 continues to burn fuel while in this frozen state. When my freezes end, the plane has not moved during the duration of the freeze, but there is less fuel on board. I wish I knew what that meant.

Mine starts freezing over Greenland, too! Flying KJFK-VHHH, she hums along nicely until somewhere over Greenland, then I see repeated freezes lasting 5 to 15 minutes, but if I let it go it eventually seems to somehow settle down after heading south over Asia and then I don't see any more freezes until the end of the flight. I've been wondering whether the length of the flights I've been attempting has something to do with this. It only seems to start when I'm a good 5 or 6 hours into a 15+ hour flight. I've tried disabling all my extras, including FSUIPC autosave, Opus weather and UT2, but still get the freezes. Another thing I tried was to delete my Logbook.bin file. I found some old forum messages indicating that it could be a source of freezes. That hasn't cured the problem, either, although at first it seemed that I was getting the freezes less frequently. Frustrating.

I've relegated this plane to the hangar due to a couple of serious drawbacks. These matter to me, but they might not matter to you. There are no pop out PFD or ND or ECAM gauges, so it is very difficult to get good crisp undocked displays of those gauges onto a second monitor. It may be possible, but I've given up trying. The visual quality of the gauges is not what I hoped for. (They do provide a pop out for the left MCDU.) When I bought this plane, I didn't think this would be such a big deal, but I've gotten to the point where it's now an absolute dealbreaker for me. There are other planes I can fly which have a much better display of the primary flight instruments, so I just don't fly this anymore. This plane just won't work if you change the simulation rate to anything other than 1. You simply cannot accelerate, even to 2x. That may or may not matter to anyone else, but I do find it annoying. Just my opinion...