I think if the whole world came crashing down on MSFS, I have a feeling that the 737 will still be a role model in performance and fps resources. Don’t know what PMDG did and I don’t know what wizardry they used.
They used WASM modules for the 737. This code compiles on first run (hence the long wait time) and executes directly within the sim itself, which significantly improves performance over the more traditional JS-coded aircraft. The FBW A320 and Fenix A320 use mainly JS (plus the Fenix external program), which will always have a performance hit when compared to WASM.
Unfortunately, WASM comes with limitations, which is why the PMDG 737 doesn’t currently allow direct importing of Simbrief flight plans from the web. These will be improved once Asobo removes some limitations of WASM.
Very useful info. Thanks. I’m hoping once Asobo removes those limitations, those occasional micro-stutters and pauses will be a thing of the past with the A32NX. I’m one of those unfortunate ones who experience this and it only happens with the A32NX.
Do you know if the CRJ uses WASM as well?
Yes it uses WASM as well, which is why the CRJ doesn’t have a working terrain and weather radar. Asobo has not developed the API to allow WASM to call on the built-in terrain and weather radar bitmaps. JS aircraft can call on this API for the weather/terrain map, which is why the FBW A320 and other aircraft have this working (or did work, in the case of FBW).
SU10 has added an API for WASM compilations to use the in-game weather radar bitmaps, which means PMDG can add the weather radar. However, from what I understand, the API is pretty basic and doesn’t allow much customization of weather radar bitmaps. The PMDG will get a working weather radar, but I don’t think it’ll be as advanced as users might hope.
Again very informative. I knew there was something going on in the background which is in common between the CRJ and 737. Thanks for the explanation.
This is all very interesting. Heard about these terms before but didn’t really understand it. With the aircraft that do directly link to simbrief so CJ4/CWT FMS, FBW A320 is it fair to say that this only works because they are using JS and not WASM. Whereas CRJ and 737 don’t because of WASM?
How will the upcoming EFB with the 737 get around this to interface with simbrief?
Correct, one of the big limitations right now for WASM is that it cannot communicate with the outside internet - it’s essentially a sandbox running within the sim itself. Aircraft that use JS, like FBW and Fenix, aren’t limited by this and have EFBs that can display almost anything from the internet, like real-time weather maps and flight plans. I believe Asobo has already communicated they intend to address this in the future, but I don’t think I’ve ever seen a timeline.
One of the benefits of using WASM is that it can be created from a C++ project, meaning PMDG could quickly convert their C++ legacy coding used for FSX/P3D to WASM. It’s understandable PMDG went this route, as it allows them to reuse their existing legacy coding.
I don’t know what this means for the PMDG EFB, as it would clearly be limited with respect to outside internet access. I would imagine PMDG would first develop essential calculators for the EFB, like a takeoff and landing distance calculator, then add more advanced functions as allowed.
Well i can tell you that my FPS appreciates that sandbox very much. Yes it’s a bit of an extra step to manually place the simbrief plans inside the work folder. Simbrief downloader app makes it a bit less time consuming…and i’ll take that for now.
What is being done about the fuel burn while paused?
There is nothing preventing a developer from mixing JS/HTML and WASM in a single project. Undoubtedly the upcoming EFB for the PMDG will be coded in JS/HTML while the main aircraft systems and displays will remain in WASM.
That did cross my mind, but not being a programmer I wasn’t sure. So we can assume then that the FMC is completely WASM at the moment then but the EFB may be JS/HTML that interfaces with the WASM.
I’ve heard all these terms before, but it’s interesting to know the various techniques involved.
Yes, the PMDG EFB would have to be JS/HTML if it is going to have the ability to communicate directly with Simbrief for flight plans and weather, and Navigraph for charts, because pure WASM does not support that.
Lots of talk about the upcoming EFB seems … misinformed? RSR has talked about these things generally for months in periodic development updates on the PMDG forums. As I understand it (and I may be wrong), Asobo is changing/expanding the functionality available to WASM code to allow integration with various types of external data - specifically the types of data necessary to import Simbrief plans and possibly display PDFs (legacy PMDG products had this capability in their EFBs).
I don’t think the EFB will be javascript at all, but instead another chunk of C++ compiled into WASM. Hopefully we will get some preview info of the EFB in the next couple weeks, per the last update we got when the -800 was released.
Yes, that’s the plan to address the WASM limitations. However, those changes have not yet happened, which opens the discussion to exactly what PMDG will model with the EFB until then. As far as I’ve seen, there hasn’t been a detailed reveal from PMDG about what features exactly will be implemented on the EFB at release.
RSR and other developers have access to and are working with the SU10 beta SDK and have been in communication with Asobo directly - they know better than most what is going to be available and what is not. I read their comments with that in mind.
The most recent update from PMDG says they EFB will be modular, lightweight and expandable over time. They plan to start testing it with their beta team by mid-September and released a few weeks later. Prior updates have indicated that they already have Simbrief integration and chart display working.
I presume we will get some more updates soon.
Anyone else getting these white squares on the displays when moving your head (TrackIR) or panning the view?
The longer this takes, the more dissatisfied I’m becoming. Given that other higher-level sims like the CRJ and A320 come with EFB’s of varying levels of functionality, the fact that we are this long after release and still have nothing (not even a unit well into Beta testing) is quite annoying. Now the info above that PMDG will add features to the EFB after release. One could take that as meaning we’re going to get a very basic unit (similar to the CRJ) and PMDG will bring it up to an acceptable level whenever they get around to it. Before all the PMDG fan boys jump on me, note - I love the jet, to me it’s the 2nd best out there, my annoyance is mainly directed at the missing EFB.
None of this is new or secret information. PMDG have been discussing things since the -700 was released in May.
But life’s too short to carry around angst - if you’re dissatisfied, go fly something else. No one is stopping you.
And here comes the fan bois. Thought I made it clear that I enjoy the PMDG product? Apparently, I neglected to observe the forum golden rule - Thou shall speak no evil of PMDG - ever. Please re-read my post. My dissatisfaction was directed at PMDG’s handling of the EFB introduction, not the sim in general.
Which, AGAIN, is not nor has it ever been a secret even before you bought the plane.
And please don’t call names. It’s rude.