WX RADAR might be the cause of the majority of WASM crashes

[leo5now]

So I may or may not have narrowed down the cause of WASM crashes. 

I tested this 6 times using a variety of methods using the famous YSSY - KLAX route and im on MSFS2024 SU2. The flight wouldn't last more than 4 hours without a WASM crash but after testing it 6 times I think I finally found the problem but it could be just out of sheer coincidence so I'll have to test it further. 

 

The solution: OFF WX RADAR

When I read previous accounts such as the bug in which you cannot use the traffic radar on the ND in previous versions, I focused back on the ND trying to find if there are other methods and I turned to the WX radar.

My theory is that turning on the WX radar constantly feeds information or new info into the WASM slowly filling it up and causing it to crash especially if you have intense weather ahead. 

Edit 1: So it turns out that inibuilds released an update months ago ensuring that the WASM module automatically deletes the unused data making space for new data to be allocated. So this can be potentially a bug or user error in the MSFS settings itself since WASM crashes is the behavior when virtual memory runs out completely or isn't allocated properly 😕

Edited June 1 by leo5now

[ewozza]

Very interesting. Are you on 2024 by any chance? 

[leo5now]

2 hours ago, ewozza said:

Very interesting. Are you on 2024 by any chance? 

yep! using 2024 and still ongoing testing, i did another flight (EFHK - RJTT) but I pushed my settings enabling AMD fg and RT Shadows and had a WASM crash 4 hrs into the flight. According to FSElite, it's when you run out of VRAM or when the VRAM isn't properly allocated. So right now im testing with RT shadows off and Nvidia FG on. As well inibuilds already released an update when it deletes previous data inside the WASM module so im not entirely sure if this is a random bug or it could be just user error in terms of the PC specs and how the user sets up the settings in MSFS that causes the Virtual Memory to run out.

When im done with this flight right now which is (EFHK - RJTT again), I will do another one but this time with WX radar turned on keeping the settings the same. 

Yes, I do have a lot of time on my hands to troubleshoot this cause I rlly wanna fly this bird hahahahaha

Edited June 1 by leo5now

[ewozza]

Your findings are really important especially considering I cant get into the plane for long hauls massively regularly (and to be honest my enthusiasm is low to fly this), due to the WASMs I experience about 90% failure rate on this bird. 

V1.0.10 was good, really stable but V1.0.11 is back to the same old same old. Mine is the same, very much around the 4-6 hour range where it'll WASM. So please do report back!

[Xenon341]

And don't forget to post the WASM logs as asked by ini in case of WASM crashes.

[leo5now]

4 minutes ago, Xenon341 said:

And don't forget to post the WASM logs as asked by ini in case of WASM crashes.

Yep will do! Actually majority of my WASM crashes do not show the error message in the module which is more complicated since idk if it's from ini or MSFS or just when you ran out of virtual memory.

[leo5now]

21 minutes ago, ewozza said:

Your findings are really important especially considering I cant get into the plane for long hauls massively regularly (and to be honest my enthusiasm is low to fly this), due to the WASMs I experience about 90% failure rate on this bird. 

V1.0.10 was good, really stable but V1.0.11 is back to the same old same old. Mine is the same, very much around the 4-6 hour range where it'll WASM. So please do report back!

In the first test run - FG OFF, RT SHADOWS OFF, DLSS DLAA enabled, and WX off and ARPT off using the YSSY - KLAX route, I was able to push the plane up to 10 hours and then I had to leave it cause I had something in the morning so I wasn't able to land. 

[ewozza]

Positive move. I might try a flight tomorrow overnight with WX off completely and see how it behaves. Will make my own thread on findings (if any) and link you here @leo5now

[leo5now]

3 hours ago, ewozza said:

Positive move. I might try a flight tomorrow overnight with WX off completely and see how it behaves. Will make my own thread on findings (if any) and link you here @leo5now

Happy to report that the flight im doing right now (EFHK-RJTT) with RT SHADOWS OFF, TAA, NVIDIA FG, and W/X OFF/, ARPT off, has reached the 11- hour mark!! but then i realized i didnt have real world weather on...y is this not on by default

Edited Monday at 12:16 AM by leo5now

[leo5now]

On 6/1/2025 at 7:52 AM, leo5now said:

So I may or may not have narrowed down the cause of WASM crashes. 

I tested this 6 times using a variety of methods using the famous YSSY - KLAX route and im on MSFS2024 SU2. The flight wouldn't last more than 4 hours without a WASM crash but after testing it 6 times I think I finally found the problem but it could be just out of sheer coincidence so I'll have to test it further. 

 

The solution: OFF WX RADAR

When I read previous accounts such as the bug in which you cannot use the traffic radar on the ND in previous versions, I focused back on the ND trying to find if there are other methods and I turned to the WX radar.

My theory is that turning on the WX radar constantly feeds information or new info into the WASM slowly filling it up and causing it to crash especially if you have intense weather ahead. 

Edit 1: So it turns out that inibuilds released an update months ago ensuring that the WASM module automatically deletes the unused data making space for new data to be allocated. So this can be potentially a bug or user error in the MSFS settings itself since WASM crashes is the behavior when virtual memory runs out completely or isn't allocated properly 😕

Scenario 1: FG ON, RT SHADOWS OFF, W/X RADAR OFF and ARPT OFF - Completed no WASM crashes

Testing soon same settings but with weather radar on and arpt on now to see if it will affect the flight

also important to note that the OANS wasnt used in the departure airport so I will be doing a full typical setup on the A350, like what everyone does for a flight

Edited Monday at 01:44 AM by leo5now

[ewozza]

Just curious, when you select W/X off where are you doing this? Are you turning the system off completely along with Predicted Windshear system within the SURV page? Or are you just not selecting WX on either Captain or FO's ND screen?

This would bring up a amber warning on the EICAS I believe. 

 

Edited Monday at 10:42 AM by ewozza

[leo5now]

6 minutes ago, ewozza said:

Just curious, when you select W/X off where are you doing this? Are you turning the system off completely along with Predicted Windshear system within the SURV page? Or are you just not selecting WX on either Captain or FO's ND screen?

This would bring up a amber warning on the EICAS I believe. 

 

just the WX on the ND both off on CAPT and FOs

Edited Monday at 10:47 AM by leo5now

[Eddie]

Thank you all for the very thorough testing. We'll take a look alongside you and see what conclusion we can reach. 

[leo5now]

4 minutes ago, Eddie said:

Thank you all for the very thorough testing. We'll take a look alongside you and see what conclusion we can reach. 

Hello! Thanks for responding to the thread!

I think I'm calling it here that the weather radar or any additional information on the ND that constantly adds to the WASM module doesn't affect the WASM crashes. It had before in previous versions, like the glitch in which the TRAF radar on the ND would cause a WASM crash, but in this version, nothing. The flight I am testing right now, RJTT-LFPG, has also reached the 11-hour mark, so this is likely due to user error, where users may not have optimized their settings to account for Virtual Memory usage. VRAM is important, but VM reaching its limit is where the majority of the WASM crashes happen. I'd just recommend users keep an eye on their VM, leave about a 4-5 GB buffer during mid-flight, and then they should be good. FG is also fine, but just make sure it doesn't max out the VM or the VRAM. 

But feel free to test it out cause in my case, none of the systems here in the plane have any role in contributing to a WASM crash in V1.0.11 atm

[ben4muk]

I too am suffering from WASM Crashes.  It got MUCH WORSE since 1.0.11.  Every flight is WASM Crashing.  Is there something unique about the Time Compression?  What I am doing is, WASM Crashing, then I load an Autosave, and apply the time compression, and I am able to complete the flight.

[ben4muk]

Or, perhaps, there might be something happening in the early stages of flight that triggers it.  And then once you reload the flight after, and skip the early stages, you are "safe" from a wasm crash?

[leo5now]

22 minutes ago, ben4muk said:

Or, perhaps, there might be something happening in the early stages of flight that triggers it.  And then once you reload the flight after, and skip the early stages, you are "safe" from a wasm crash?

R u using SU3 Beta? 

[ben4muk]

10 minutes ago, leo5now said:

R u using SU3 Beta? 

Negative!  SU2!

[leo5now]

35 minutes ago, ben4muk said:

Negative!  SU2!

Hmm... i tried to disable the weather radar on the ND during mid-flight, but I still got a WASM crash. It wasn't until I realized that I had RT shadows on so I turned it off, and all of a sudden, there were no WASM crashes 😄

Edited Monday at 05:15 PM by leo5now

[ben4muk]

1 hour ago, leo5now said:

Hmm... i tried to disable the weather radar on the ND during mid-flight, but I still got a WASM crash. It wasn't until I realized that I had RT shadows on so I turned it off, and all of a sudden, there were no WASM crashes 😄

Yeah, well...  It looks like I spoke to soon...

 

[Simicro]

I got the A350 last week-end and had my 1st WASM today during a LFPO-LIML short flight. The WX radar was on since the beginning of the flight and when the WASM occured there was intense weather ahead. I'm not knowledgeable enough to provide more details or insights but just wanted to help you with your theory.

[leo5now]

I'd recommend reinstalling the aircraft fully and clearing out the WASM folder for those experiencing the WASM module crash. Before, when a WASM crash happened, for me, it wouldn't indicate the cause in the debug menu, which was weird. If you've verified that it's a WASM crash with the message in the debug menu, then try clearing out the WASM folder or reinstalling the plane if the problem persists. That's what Inibuilds always recommends to users

[leo5now]

Well, it looks like my luck caught up to me, I had a WASM crash after 10 hrs of flying

RKSI - KSFO, was planning for the arrival until Oakland recleared me to a visual. After changing from ILS to visual approach, the MFD froze and had a WASM crash, this is just insane now. Back to the drawing board, I guess...

[Peter]

Bummer guys... Im finding turning off ALL AI traffic gives me better performance and no crashes. The planes look stupid anyways. No biggie

 

Edited Tuesday at 09:27 PM by Peter