WASM Crashing

[CR7]

Hello there. 
Today, I had the first WASM Error after v1.0.1. The WASM carshed when I clicked the INSERT of the received f-pln. Trying to fly from RJTT to RJCC.
PS:

Aircraft: A350-900

Simulator: FS2020

Navdata Method: SIM DEFAULT
i9-13900k
RTX 3090
RAM 32GB
 

[richboy2307]

Hi @CR7

Are you having this crash repeatedly upon F-PLN import or only one instance?

If you've had it more than once, are you getting it specifically on this route only? Or can you reproduce the crash on any import.

Thanks!

[CR7]

8 hours ago, richboy2307 said:

Hi @CR7

Are you having this crash repeatedly upon F-PLN import or only one instance?

If you've had it more than once, are you getting it specifically on this route only? Or can you reproduce the crash on any import.

Thanks!

I got the same WASM crash in V1.0 and V1.0.1 versions. The first WASM crash in V1.0 was preparing from LFBO to EDDF.

I also see the almost same upon F-PLN WASM crash issues in dc. 

 

Edited March 4 by CR7

[richboy2307]

@CR7
Thanks.

Yes users have reported this issue and we have addressed identified causes in the v1.0.1 update already.

Can you confirm you cleared your WASM folder before launching the 1.0.1 update? This will force a fresh WASM Compilation and ensure you're running the latest code.
If not yet done, please try now:

Over the past few hours we've tried to reproduce your crash internally and via our other testers but not able to do so. Personally I've tried to import over 50 times, on both SIM DEFAULT and NAVIGRAPH navdata sets and am not yet able to induce a WASM crash doing so.

It would be great if you could record a video as below of the crash happening with your console window open in order to help us exactly recreate your steps.

 Thanks!

[CR7]

22 minutes ago, richboy2307 said:

@CR7
Thanks.

Yes users have reported this issue and we have addressed identified causes in the v1.0.1 update already.

Can you confirm you cleared your WASM folder before launching the 1.0.1 update? This will force a fresh WASM Compilation and ensure you're running the latest code.
If not yet done, please try now:

Over the past few hours we've tried to reproduce your crash internally and via our other testers but not able to do so. Personally I've tried to import over 50 times, on both SIM DEFAULT and NAVIGRAPH navdata sets and am not yet able to induce a WASM crash doing so.

It would be great if you could record a video as below of the crash happening with your console window open in order to help us exactly recreate your steps.

 

 Thanks!

Hi there.

Thank you for following up. 

I can confirm I did not clear my WASM folder before launching the 1.0.1 update. I will do it and run some flights for testing. 

However, the crashing is random. I am not sure if I can do the record when the WAM crashes.

 

My WASM folder has more files in here than you showed. Should I delete all of them or just pick the flies that you showed? 

 

Edited March 5 by CR7

[richboy2307]

2 hours ago, CR7 said:

I can confirm I did not clear my WASM folder before launching the 1.0.1 update. I will do it and run some flights for testing. 

Ok. I'm hoping that resolves it for you.

2 hours ago, CR7 said:

My WASM folder has more files in here than you showed. Should I delete all of them or just pick the flies that you showed? 

That's fine, it will vary per sim and installation. But just delete everything you see there. It will all be re-generated on next launch of the aircraft. Do remember to re-do your throttle calibration as that too will be reset.

2 hours ago, CR7 said:

However, the crashing is random. I am not sure if I can do the record when the WAM crashes.

Yeah that is the issue I'm afraid. Regrettably, from our testing so far of reported crashes, very few of them are reliably reproducible as they're very case-specific instances and require close matching of conditions to reproduce. If we can reproduce the crashes, we can observe them via debugger and then resolve them. However without that, we're guessing at best and there is no way to verify that any fix is even working.

Nonetheless, we are committed to resolve these instances of WASM crashes and improve stability for all. The team is working tirelessly to that end but we also require your help to report them as they happen, especially the reproduction steps.

Thanks!

[CR7]

On 3/5/2025 at 2:34 AM, richboy2307 said:

Ok. I'm hoping that resolves it for you.

That's fine, it will vary per sim and installation. But just delete everything you see there. It will all be re-generated on next launch of the aircraft. Do remember to re-do your throttle calibration as that too will be reset.

Yeah that is the issue I'm afraid. Regrettably, from our testing so far of reported crashes, very few of them are reliably reproducible as they're very case-specific instances and require close matching of conditions to reproduce. If we can reproduce the crashes, we can observe them via debugger and then resolve them. However without that, we're guessing at best and there is no way to verify that any fix is even working.

Nonetheless, we are committed to resolve these instances of WASM crashes and improve stability for all. The team is working tirelessly to that end but we also require your help to report them as they happen, especially the reproduction steps.

Thanks!

Hello there,

I had WASM crashing again. 

The plane is cruising, and when I move the map to select an exit for BTV, WASM crashes!!!

Last time it was the A350-900, this time it's the A350-1000's turn!!

 

Edited Friday at 05:56 PM by CR7

[CR7]

On 3/5/2025 at 2:34 AM, richboy2307 said:

Ok. I'm hoping that resolves it for you.

That's fine, it will vary per sim and installation. But just delete everything you see there. It will all be re-generated on next launch of the aircraft. Do remember to re-do your throttle calibration as that too will be reset.

Yeah that is the issue I'm afraid. Regrettably, from our testing so far of reported crashes, very few of them are reliably reproducible as they're very case-specific instances and require close matching of conditions to reproduce. If we can reproduce the crashes, we can observe them via debugger and then resolve them. However without that, we're guessing at best and there is no way to verify that any fix is even working.

Nonetheless, we are committed to resolve these instances of WASM crashes and improve stability for all. The team is working tirelessly to that end but we also require your help to report them as they happen, especially the reproduction steps.

Thanks!

I got the other WASM crash on the same day again!!

The WASM crashes when I release the flap 3 on the final approach to KTDW by (inibuilds) 22L.

I can confirm that all the WASM crashed after I cleared all the WASM files before launching the A350. It looks like the different crash type of the WASM!!!