Skip to content
View in the app

A better way to browse. Learn more.

iniBuilds Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

WASM Crash on MSFS 2020

Featured Replies

I encountered a very strange behaviour this evening where the A350 displays got frozen some 200ft above the ground. Every in the airplane frozen but the airplane kept flying and I was able to land it visually. Once on the ground nothing worked including throttles which were stuck in climb detent position. Have a look at screenshot below - I'm parked up on gate yet everything is still frozen. I was flying the RNP approach to runway 09R into London Heathrow with Navi graph charts loaded onto OIS

 

20250324004900_1.jpg

The system froze when I was on the ground and importing the flight plan in Simbrief.

  • Staff
7 hours ago, UA124567 said:

I encountered a very strange behaviour this evening where the A350 displays got frozen some 200ft above the ground. Every in the airplane frozen but the airplane kept flying and I was able to land it visually. Once on the ground nothing worked including throttles which were stuck in climb detent position. Have a look at screenshot below - I'm parked up on gate yet everything is still frozen. I was flying the RNP approach to runway 09R into London Heathrow with Navi graph charts loaded onto OIS

 

20250324004900_1.jpg

Thank you for your report. Can you confirm you are running v1.05

  • Author
8 hours ago, haza2 said:

Thank you for your report. Can you confirm you are running v1.05

I was on v1.0.4 earlier and had flown numerous flight since installation and never encountered a single wasm crash before. 

I have updated the A350 to v1.0.5 earlier today and have flown both A359 and A35K for same approach I tried last night and this time every thing worked like it should be. I'll continue to monitor this and make another report if I do encounter wasm crash again. 

On 3/25/2025 at 1:25 AM, UA124567 said:

I was on v1.0.4 earlier and had flown numerous flight since installation and never encountered a single wasm crash before. 

I have updated the A350 to v1.0.5 earlier today and have flown both A359 and A35K for same approach I tried last night and this time every thing worked like it should be. I'll continue to monitor this and make another report if I do encounter wasm crash again. 

Unfortunately, in version 1.0.5, they still haven't completely fixed this issue. I encountered it again today when entering the approach procedure while descending on UUEE-ZSAM. When I updated the version, I deleted the WASM folder before downloading the update just like the previous 4 updates, so I think there is nothing wrong with my operation. Combined with the wasm crash reports that have appeared online in the past week, I can hardly find any pattern. It is like a ghost and has the probability of appearing at any time at any stage of flight, especially when you are operating EFIS. Version 1.0.5 may reduce the probability of this problem, but it is still not zero.

Create an account or sign in to comment

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.