Unable to effectively test the SU16 beta as any aircraft that use WASM appear to be inoperative. A message appears on the aircraft selection screen indicating “missing content” for any 3rd party aircraft that utilize WASM (ALL PMDG products, Aerosoft CRJ, Justflight products, etc.).
Regardless of the error, I attempted to load into a flight in these products, and found the aircraft to be useless.
I deleted and reinstalled the “Add-on Support” app, but this made no difference.
This is very reminiscent of the 1.37.15.0 build of SU15 Beta back in May of last year. The issue was quickly fixed then, so hopefully this can be promptly corrected.
I didn’t get this error. What I did get was a WASM crash at Asobo Innsbruck after I’d finished setting the aircraft (A20N v2) up and was requesting taxi from ATC
Restarted the flight and it was fine second time around. Now in the air towards Schiphol by Feel There for which runway lights never work - let’s see how it gets on with SU16 and the apparent memory improvements
To give some closure to my post, landed at Schiphol (Feel There) and the runway lights were indeed working for the first time on 2020. So we may have a winner with this update
On a side note, I decided to push the sim to the max and continue on to Bari (also 3rd party) without ending the flight but unfortunately it wouldn’t refuel the aircraft from the EFB like it normally would and the weight and balance page didn’t work either so had to end the flight
I’m going off on a slight tangent, but you can refuel the aircraft no problem but once you do the “master avionics shut down” trick to get the logbook entry on the screen and then press continue, it no longer lets you do it
Edit: just tried it again after pressing continue having already set my fuel for the next leg and it let me change it. This sim is so random
But back on the subject of WASM, my friends are finding that WASM isn’t working at all on PMDG aircraft in this beta
We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.
If you try to select a WASM aircraft like the inibuilds A300 or the PMDG 737 you get a warning that the required content is not installed. Loading in anyway the cockpit is completely frozen with the yoke fully deflected off to the side
WebAssembly (WASM) in Microsoft Flight Simulator is a way for developers to run custom cockpit instruments and systems that work on both PC and Xbox. It lets them write the code in C++, which then gets packed into a format MSFS can safely and efficiently run.
Same here (as mentioned in performance thread). PMDG 737 does not initialise - all panels blank and yoke stuck hard to the left. I have also had an intermittent error message when selecting the aircraft along the lines of ‘you don’t have all the packages to use this item, please restart’ (apologies I’m paraphrasing from memory).
I’ve been thinking about this new beta today (maybe it’s just my late-night brain), but I’m honestly stumped.
You wouldn’t expect a bug like this to make it into a beta if Microsoft knew about it ahead of time. And sure, we’ve seen betas introduce “known” issues before—but this one feels like it should have been caught.
Given the last 6+ months and the miss promise of this SU etc. It’s a pretty big deal, especially for some Xbox users like myself, who are still flying in 2020 because it’s the only way we can run complex third-party add-ons.
This kind of issue makes you wonder if the beta was even tested with those WASM aircraft at all. (Or maybe I’m just clueless on this stuff)
I’m definitely holding off on installing it until this is fixed. And before someone chimes in with “that’s what betas are for”—yeah, I get it. But at this stage in the sim’s life, we shouldn’t be seeing bugs of this magnitude. Right?! Sorry… again it’s late for me and I should probably keep my thoughts to myself…but It doesn’t exactly inspire confidence.
Anyway, here’s hoping they fix this quickly—and that whatever final SU ends up being next for 2020 doesn’t turn into another step backward. Xbox users have seen that happen once before.
Edit: I see it’s been bug-logged. That’s good news at least. (let’s hope it’s a simple fix.)
Agreed, considering that 2024 appears to be essentially dead in the water for us Xbox users until something miraculous happens, would really love to see this SU land on its feet. Not too upset that this made it into the beta and it does affect third parties after all so not really Asobo’s issue…but again hard to understand how things like this, plus the mouse/EFB issues in 2024, keep being pushed out to consumers…
