All Activity

Seriously, these pesky wasm crashes need more attention. Hopefully SU4 has fixed this... not oldingmy breath or anything

I suspect this is a unique situation for you. Our virtual airline's rules require us to start and end all flights at the gate or ramp. Despite this, I occasionally experience this issue myself.

Hello, If clearing your cache folders as well as reinstalling the iniManager does not resolve the issue, please reach out to our direct support. Include you have already tried the mentioned steps but to no avail. Thank you

Hey dear team, First off — holy wow. The A350 performance boost in SU4 is insane. I genuinely didn’t expect a heavy, systems-rich airliner to run this smoothly, but you absolutely nailed it. Huge kudos! Since you clearly have some magic going on under the hood: like many simmers, I’ve got the Winwing MCDU, and once you get used to using a real hardware CDU, it’s hard to fly without it. It would be amazing if the A350 MCDU and/or EFB supported external access — e.g., via an iPad or a web interface. Please please ... If you could add native remote MCDU/EFB support, that would take the A350 to the next level and really justify the premium tier. 😉 Thanks for all the hard work!

With all due respect. You created your report on a Sunday. We are working through the created topics that came through over the weekend. Please have some patience. I've forwarded your report to the team. Thank you

I notice this as well. With the Ini 'POI models' un-ticked (MSFS 2024 KLAX Enhanced) you end up with the massive crater when the 'SS3D Sofi stadium' option is enabled or disabled along with SS3D Los Angeles activated within it's config tool. If I disable the SS3D Sofi stadium option and enable the inibuilds 'POI models' I end up with the stadium but the horse track also shows. So what are the option/s using with SS3D Vol 1 US Modern City? Also should the SS3D scenery be higher priority (further down list) than KLAX?

For me and doing normal flight even when starting at gate I know already I will have a crash at some point

Same here! After the SU4 update yesterday I am getting those red screens with WASM crash notofication, whenever I load the A340 at a runway. Also the landing gear is missing. When I start from a gate everything is fine. Also autosave does not work. When loading an autosaved scenario, the captain's side window will open, no matter if midair or on the ground and the PFD screen goes blank. Just for info: I have the A340 downloaded, not streamed. After having above issues yesterday I uninstalled the A340. The plane was then autonatically streamed and everything was fine. I then downloaded the plane again and it also worked for one time when starting on a runway. After then loading an autosaved scenario, all the issues were back.

I found if I start A340 from ramp, there is no WASM crash, but If I start A340 from runway, it always crashes with reds

In the manual its says to press Left Ctrl key to activate keyboard input. But when I press that key the orange message is not appearing and I cannot use my keyboard to enter values. My specs; Xbox X, external keyboard, SU4, v1.1.8). Do I have to map the key or is it a bug?

Hello, This morning, I wanted to take a long flight. But after about an hour or two, the plane's controls froze and veered off course. When I returned to the computer, I was met with this surprise. Apparently, this problem is still ongoing. (My airline also suspended me for this reason 😅. Thankfully, they forgave me this time, and I was able to return.) Believe me, I'm really tired of these unpleasant surprises. I was glad these problems ended with Su4, but apparently Su4 hasn't fixed this problem either. Please find a solution to these problems. And test them thoroughly before releasing them. I think all these problems started after version 1.0.3. If necessary, give us a temporary downgrade to that version. Now, let's enjoy our flights. (I'll add screenshots.) Sincerely,

I just can't understand one thing: why create posts about WASM crash, if the developer doesn't respond to them!!!???

Same issue here. Also the engine doesn't seem to 'wobble'? (specs; xbox X, SU4, v1.1.8, aircraft streaming)

We are the same

Hello @LukeSkyBellic @flyalongswithdan I had the same issue with the a340 when doing FRA - SJO. I was about to create a custom waypoint for the ETOPS and when I entered coordinates, red screens occurred. It's really annoying we getting wasm crash at each flight and it's so random. Hoping for a quick fix because we can't fly without the stress of having wasm crash.

Hi, How do you enter this in this flight plan in the FMC? Are these waypoints supported? "22N060W 27N056W 34N050W, etc," TNCM DCT PJM M576 OBIKE DCT 22N060W 27N056W 34N050W 40N045W 46N040W 48N030W 48N020W 48N015W DCT OMOKO DCT GUNSO DCT RATKA/N0458F390 DCT LARLA/N0426F400 DCT GANTO/N0421F390 DCT JSY/N0385F320 UY111 INGOR/N0356F280 UM25 LUKIP LUKIP9W LFPG MSFS2024 SU4 Thanks, Daniel

Hello inibuilds, Have you fixed this bug in SU4? Regards

When I enter a STAR or runway (at RJTT in my case), this happens. I notice it happened to another user in the A340 forum too so clearly not type-specific. Recently updated to SU4 on MSFS2024 so probably that since this has been working fine for the last 2 weeks that I've used it daily. I reinstalled it and did the delete WASM folder thing the first time. This is after full reinstall. Thanks for assistance, Dan

I just came here to share exactly the same thing. I recently updated to SU4 (MSFS2024). Never had this issue. It happens when I insert the arrival for Tokyo Haneda in my case (RJTT). I do hope a solution is found. I uninstalled and reinstalled (the 350) yet it happened again. (Oh, this is a 340 forum... well, the same issue applies!)

Every time I enter a coordinate in DATA it goes into WASM CRASH!

WASM crash?

Not great really. Looking online this first got raised back in June and nothing has been done.

Sadly, I’ve still not seen or found a solution to this yet.