is available in OC3

You can read below what Randazzo said about the 737 update using the link below:

https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/402293-14jul26-737-fleet-update-bastille-day-wasm-issues-and-some-other-bits-for-you-this-week

I can't summon the energy to read these

I had absolutely no problem reading it. The best part is that an update for the 777 should (hopefully) be available by the end of this week (which apparently includes a fix for the pitch oscillation issues). The worst part is that it does not include the new PMDG 777 sound package. Not a disaster, but I really want to hear what they can do after being very impressed with their new 737 sounds.

Really eager to see the marketing previews of the 747

3 hours ago, xsever said:

You can read below what Randazzo said about the 737 update using the link below:

https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/402293-14jul26-737-fleet-update-bastille-day-wasm-issues-and-some-other-bits-for-you-this-week

Thanks!

This is build 4.0.56.

This build addresses code stability throughout the aircraft code files, with specific fixes for:

• Persist Engine Exceedance in Panel States

• Manual Airway Entry Error on RTE Page

• Disconnect Annunciator Flash

• Arc Magvar and Bridge Arc-to-Line Gap

• Low Brake Hydraulic Pressure Error

• PERF INIT FL Error

• EFIS/ND Rendering Issues

• Line Draw Gaps

Those who want to keep reading RSR's post here may click on the spoiler

RSR Wall of Words

[14JUL26] 737 Fleet Update, Bastille Day, WASM issues and some other bits for you this week!

Yesterday, 20:20

Captains,

If you spend any time at all with us, you recall that at PMDG we go through cycles of noise and silence. As a project nears release or gets new features in the post-release phase, we have plenty we can show you and thus we make quite a bit of noise. During the heavy work cycles, where new products and features are being constructed, much of what we do is the behind-the-scenes grunt-work that doesn't lend itself to videos or screen captures- and as such we tend to get a bit quiet.

To put it another way: Here at PMDG, unlike with kids or dogs- "quiet is always good news."

We are currently in one of those quiet phases, but we have some things to share with you that are important, so it is probably good that they will stand out from the silence of the past few months.

PMDG 747:
If you wander past the front door of the 747 hangar, you will see the vast majority of our developer resources are currently hard at work preparing the first of our 747 titles for initial Alpha Testing. We have set an ambitious product specification down for this, our first title and the team is working diligently through the deliverables that will be required in order to put the product into beta testing. If you have ever run a big project, you can probably relate to how such an ambitious project tends to come together all at once- but in the lead-up to that moment the work can become quite tedious and "never ending." We are deep into that never-ending work phase right now, but the airplane is just about ready to begin alpha flight testing, which will lead rapidly to beta entry and then to your hangars.

We have spent some time putting together a comprehensive preview marketing program- and I am looking forward to kicking off that process and seeing your enthusiasm build as we take you with us through the last phases of this ambitious project. This project and the way we introduce her to you will be different than anything we have done previously- and all of us are quite excited about it!

PMDG 777 for MSFS 2024:
Two weeks ago we pulled a few members of the dev team off the 747 and had them working through some issues that need cleanup in the 777 fleet. The 777 is in an advanced and stable state, but in the continued effort to improve the product we accidentally had a few quality problems with pitch oscillations, magenta line issues and some other handling mishaps that were annoying but probably not unexpected given the significant earlier update to those same systems. The results of this cleanup effort went into testing on Monday, and we hope to release them to you in time for your weekend flying.

Keep an eye out in the Operations Center for that update- but we'll be sure to shout it out here as well once it releases.


PMDG 737 for MSFS 2024:
Today we have released a maintenance update for the 737 that, like it's bigger sibling, has received some attention to resolve a few issues that have crept in and become annoyances to users in daily operation. Some magenta line issues, as well as a few small system issues and drawing/rendering improvements make up the bulk of visible changes as a normal part of our process for continually improving product quality.

What you cannot truly see however- may well be something that is the most important update this product has received since release- which is why I am separating it below into a unique topic.

WASM Crashes are a Threat to Simming:
All of us have been affected by WASM crashes to some degree or other. If it didn't happen to you, it happened to someone in your group flight or you have seen discussions of them in this community and wondered if the problem is out there waiting to find you. Or it hit as soon as you loaded your carefully planned flight, or it happened when you added a runway change to your FMS after top-of-descent.

No matter how you have experienced a WASM crash, their very existence diminishes your confidence in our products, the platform and simming as a whole. This is a terrible outcome, because eventually, frustrated simmers leave- and that damages the entire hobby.

For that reason, back in January we started a number of conversations with our customers in hope to collect as much data as possible on the sources of WASM crashes. From that data we began to look for patterns in hopes that we would come up with a set of recommendations to give to customers who are afflicted by them. In typical PMDG fashion, this caused a few of our senior developers to take a side-trip off their primary task (747 development) to see if they could develop a diagnostic process to find and cure ANY potential shortcoming in our source code, our models or our structures that might open the door to WASM crashes.

The problem at the core of their task, is that nobody seems to have a clear idea what causes a WASM crash. We have suspicions. We have read rumors. We have been told this or that has been proven to cause them- but nobody has ever provided a list of things to avoid doing and nobody has ever set forth with a way to learn from the sim "what caused this WASM crash?"

All we know is that the sim detects a problem and rejects the WASM content- thus causing your airplane to stop running and your flight is ruined.

Today, six months after the start of this effort, we do not have any answers, but we do have some hope.

Through data collection, conversation, researching and evaluation, we began to ask questions about the core stability of not just our products, but the products simmers add to the ecosystem. We spent money on other developer's DLC to mix and match and see if we couldn't find reliable ways to induce WASM crashes. It was too easy to point at the community folder and say "someone else in here is causing this problem, and the sim blames the airplane the user is flying." While this may very well be true, in our estimation- that conclusion was equal parts hopefulness and denial.

We cleaned the community folder back out and forced our airplane into corner after corner using steps learned through our conversations with all of you. We would force the airplane to fail and then try to narrow precisely where in our code it would happen so that we could diagnose why. More often than not, since MSFS doesn't report the cause of WASM crashes, we were guessing. But we found some common issues in our code. Patterns, if you will.

Next we shifted our effort to the platform developer's choice of compiler to learn its strengths and weaknesses. Every compiler has a unique personality, and this particular compiler is well known for being finicky and a bit tempestuous. We learned what sorts of things it didn't like, then changed our approach to coding certain aspects of logic in order to stay away from those areas in hopes that we'd see greater stability for customers. This resulted in thousands of small changes everywhere throughout our code.

We created tools to analyze our code for logical processes to find common scenarios that might create problems for the compiler, and evaluated everything from config files to models to ensure that no stone went unturned in our quest to root out cruft left over from previous platforms, or stray code that might lead to trouble within the MSFS 2024 platform.

All of this has been slowly getting baked into the 737 over months of updates- and stability has definitely improved. We can see it by tracking metrics in our support team.

Today's update brings a large piece of t hat learning effort to bear.

Did we cure WASM crashes? I highly doubt it. In fact, I am nearly certain we have not- especially since we still do not know what causes them. But what I am certain about right now is that the 737, effective with today's release, is a much more stable and MSFS 2024 friendly product than it was in December. By all rights it should be more stable than it was, which ultimately builds upon our contract with you to provide the best performance, most stable and accurate simulation of the 737 that is possible in the MSFS platform.

The changes and development best-practices we have developed from this effort will eventually get rolled into the 747 and 777 products. If we can reduce the number of WASM crashes you have by ensuring that we have done everything possible to eliminate potential faults in OUR software- then our hope is that the platform will eventually do it's part in identifying the source of problems or providing clear steps that should be taken so that ALL developers can ensure you never suffer the scourge of the WASM crash.

Navdata Issues after MSFS 5.1 Update:
One other note for you about stability today... Post SU5.1 release for MSFS 2024, we have noticed a substantial uptick in a new navdata issue with our products. The problem seems to come about when, for reasons that are unclear, some process related to the sim cleans the navdata out of the sim's /work folder, thus rendering the airplane without navdata. It is curious to note that this problem commenced more-or-less in concert with the release of SU5.1, as we had not pushed any updates in the immediate period prior to this problem being reported to us via our support team.

To cure the problem, you can manually copy the navdata into the work folder if you are on a PC- and you'll be back to normal.

1. Delete everything in%APPDATA%\Roaming\Microsoft Flight Simulator\packages\pmdg-aircraft-737\NavigationData\

2. Copy everything fromCommunity\<Aircraft>\Config\NavData\

into

%APPDATA%\Roaming\Microsoft Flight Simulator\packages\pmdg-aircraft-737\NavigationData\


If you are on Xbox, we unfortunately we do not have a remediation step for you.

We are still attempting to evaluate the issue and we do not honestly know if it is coming from the sim or something outside the sim. All of our research currently points to something changing with SU5.1. ZenDesk (MSFS support) has been telling customers "take it up with PMDG" which, if we are being honest is "Standard Punt #1" when they are more concerned with closing tickets quickly for their own reporting metrics, and less concerned with actually finding problems that can be reported back to the platform devs for handling in order to improve the customer experience.

We are making noise about it. If you are likewise affected, we recommend you do so in their support forums as well.

PMDG Products on PlayStation 5!
Welcome PS5 Users!

We have been informed that the PMDG 737-800 and PMDG 777F are now available to Playstation users. This is an exciting transition for us, as it gives us an opportunity to welcome many more new simmers to the community- and ultimately that is great for the platform, developers and the hobby as a whole.

We are hearing some new customers experiencing some problems getting their new airplanes to load/run- and we presume at this juncture that there are some hiccups in the MS/PS5 distribution that will get sorted pretty quickly. MS is just learning how to flex those muscles with the PS5 platform- and they'lll be paying close attention. We have taken the step of alerting our contacts in real time as well. Please be patient with forum/discord mods. We are happy to have new friends on the PS5 platform, but please understand that there are a couple of very large corporations sitting between you and us. We don't control the distribution chain/process, but our experience with the MS side tells us this will get resolved pretty quickly.

Robert S. Randazzo
PMDG Simulations

Edited July 15Jul 15 by DAD

I liked reading what RSR's posted here, particularly about the hunt for WASM crashes. It gives insight into the problem, what experiments have been tried to track down the issue, and what PMDG's thoughts are about the future.

6 minutes ago, Paul K said:

I liked reading what RSR's posted here, particularly about the hunt for WASM crashes. It gives insight into the problem, what experiments have been tried to track down the issue, and what PMDG's thoughts are about the future.

that may be right though the update does not fly on my end. the 737 just does not "activate". it loads fine but then freezes upon entering the cockpit, gauges remain blank, EFB is missing... did restart 2024 and no cure. deleted the WASM folder (sic!) and no cure. but I admit I am on SU6 beta, could be a compatability issue so I won't complain. though the iFly, Fenix, RJ, AS340 all work fine under SU6 beta...

I wonder if Randazzo will remember there's more to simming than just MSFS and it's bugs ?

22 minutes ago, Matchstick said:

I wonder if Randazzo will remember there's more to simming than just MSFS and it's bugs ?

Like innovation and openess to change

Before this update, my PMDG aircraft worked without any WASM issues. Unfortunately, after installing the latest update, PMDG aircraft now fails with a WASM module crash, leaving all of the cockpit displays red and unusable.

I've spent a considerable amount of time trying to resolve it on my own. I searched extensively online, including the PMDG forums, and found that I'm far from alone—many other users appear to be experiencing the same problem. I completely uninstalled the software, checked for and removed any leftover files I could find, and reinstalled everything from scratch.

To rule out conflicts, I even restored a clean Windows backup containing only a default installation of MSFS 2024, with no third-party software installed other than PMDG. After reinstalling the PMDG 737, the result was exactly the same: WASM module crash and red cockpit screens.

At this point, I'm extremely disappointed. What was previously a stable, working setup has become completely unusable after the update, despite every reasonable troubleshooting step I could think of.

If anyone has found a genuine solution or workaround, I'd greatly appreciate your help. Any ideas are welcome.

1 minute ago, LRBS said:

I'm far from alone—many other users appear to be experiencing the same problem.

Sorry to hear about your problem. I can confirm that I've seen several reports similar to yours on the PMDG forum.

I'm glad I held off on updating. These days it pays to wait a few days before updating. I wish we had the same option in MSFS.

I have a similar issue, all red screens with "WASM Module Failure", but I am on the beta so I have to expect this could happen. Is it happening to people not on the beta?

33 minutes ago, Cognita said:

I have a similar issue, all red screens with "WASM Module Failure", but I am on the beta so I have to expect this could happen. Is it happening to people not on the beta?

As said above, all dead here too. De- and reinstalled the 737, switched to default livery and still no help. No red/yellow wasm crash messages though on the displays. They just remain dark and then 2024 freezes and I must kill it.