A350 freezing in flight

[MrFickles]

For 5 times in a row on version 1.0.12 and 1.1.0, the A350 systems are freezing in fight. It happens any time between 5-15 hours in cruise. I lose all ability to control the aircraft with either the FCU or with physical controls. Along with the autopilot freeze, the PFD, ND, and ECAM are also frozen. OIS and MCDU works ok other than a loss in FPS. All other cockpit switches work fine. There are no WASM errors reported in console.

I have tried clearing WASM folder and reinstalling the aircraft, to no avail.

[Xenon341]

Hi there,

Can you add some informations requested in those instruction ?

That would help the team find the cause.

Thanks !

 

 

[Lukasz Krajnik]

1 hour ago, Xenon341 said:

Hi there,

Can you add some informations requested in those instruction ?

That would help the team find the cause.

Thanks !

 

 

Hi,

He wrote it is not a WASM crash. I have had same issue on every flight since 1.0.12. No need to do time consuming WASM crash report if we veryfied it is no WASM crash. 

[MrFickles]

2 hours ago, Xenon341 said:

Hi there,

Can you add some informations requested in those instruction ?

That would help the team find the cause.

Thanks !

 

 

This probably isn't a WASM crash.

In a WASM crash, the whole aircraft is frozen and nothing will work. Here, I can still do things like switch on and off stuff using the switches, or even mess around with the EFB/FMS. The only things that don't work are the FCU, PFD, ND, ECAM.

For reference, this is my console after encountering the issue:

Note that there are no errors shown.

[YS0430]

11 minutes ago, MrFickles said:

This probably isn't a WASM crash.

In a WASM crash, the whole aircraft is frozen and nothing will work. Here, I can still do things like switch on and off stuff using the switches, or even mess around with the EFB/FMS. The only things that don't work are the FCU, PFD, ND, ECAM.

For reference, this is my console after encountering the issue:

Note that there are no errors shown.

Strange, I just encountered something similar in my 4 hours (+1hour prep) flight and suddenly the plane can still follows the flight path, fms works, but the AP panel, auto pilot altitude hangs, the knobs can be turned but not working.. 

[Xenon341]

1 hour ago, Lukasz Krajnik said:

Hi,

He wrote it is not a WASM crash. I have had same issue on every flight since 1.0.12. No need to do time consuming WASM crash report if we veryfied it is no WASM crash. 

Yes but there are WASM crashes that don't output logs, I had some that I've reported and we are not alone.

Still reporting the same information can be useful for the dev team.

[Lukasz Krajnik]

2 hours ago, Xenon341 said:

Yes but there are WASM crashes that don't output logs, I had some that I've reported and we are not alone.

Still reporting the same information can be useful for the dev team.

How do you know if it was WASM crash if no WASM error saved in log? I had plenty of such without any WASM connection, reported some here without response from IniBuilds, neither confirmation that it is WASM. If we get WASM crashes without any log that it is WASM fault then IniBuilds is in deep… I just wonder how was it possible that P..G found workaround to this which works for most (but not every) users.

[Xenon341]

Because gauges are handled by WASM and if they freeze that means the process has a problem.

The process may have not crashed but it may became zombi. For the user it's the same consequence, instruments froze.

There is a thread here if you want some reads : https://discord.com/channels/535246634448191499/1377432283966869644

As for PMDG, well, they are not imune to it, there are several case on their discord and even a dedicated topic on their forums.

Let's hope that SU3 release will help with that for every developers that use WASM.

[Lukasz Krajnik]

So, if every gauge freeze without any trace in log in airframe build using WASM means WASM crash , what will be the benefit from reporting this? If they are random, can occure any time, any system, any situation, any input or without input, and so forth, does developer benefit from reporting even if there is nothing in the log? If this is the case, I can see point with time consuming reporting but as for now I am not sure who is supposed to fix it - FS2024 deceloper or addons developers? Who should we report to? I can not believe that none of beta testers got this WASM crash and that developer was unaware this on a release day… And last question. If WASM crashes were known already in FS2020 was it wise to use WASM? Fenix for instance did all «outside» FS and is a winner in some sens, or I am thinking wrong?
 

Edited Tuesday at 03:14 PM by Lukasz Krajnik
Spelling

[Xenon341]

Because you have to give the autosave and the OFP according to the guide and maybe the dev can detect similitude between the case.
WASM crashes don't affect anyone that as simple as it is, why you got it, why I didn't, why ini test team didn't.

As we don't know if a WASM crash is from the plane or from the sim, we report to ini. If it's a sim issue then ini will report to Asobo via the dev forum.

Fenix is not on Xbox, A350 will be. WASM is required. So winning depend of who you talk to.

Edited Tuesday at 05:30 PM by Xenon341

[Lukasz Krajnik]

If I read correctly dev forum, WASM on Xbox was/is neither error free. If addons like A350 will be equally unstable there, it will be no fun for Xbox gamers neither. And if, as you write, we don't know what causes these crashes, then I only secretly hope that all this fun with WASM won't turn out to be a dead end.

[greatnessmajesty]

Same here. The PFD, ND, and ECAM were frozen but the aircraft still flying. All the flight control input from my joystick and keyboard had no respone. However, I could swith my camera view and the sim was stilling running. I need to escape the filght in the sim and every thing lost. It usually happened if I had swithed the sim into compression mode for 4x speed.

I hope inibuild could fix this problem as soon as possible. This made the A350 nearly not usable as the filght was always incomplete.

Edited Thursday at 03:14 AM by greatnessmajesty

[Ulvar50]

Same here... on every flight over a couple of hrs.. the PFD, ND, and ECAM stop working (freezing). Making this a short-haul aircraft I guess! 
 

Edited Thursday at 08:13 AM by Ulvar50

[Xenon341]

Guys, please, "same here" doesn't help 🙂

Post the necessary informations as required by the guide 

 

[Ulvar50]

Wilco... Just going to start a new +8hrs flight, be right back!

Edited Thursday at 12:19 PM by Ulvar50