v1.2.5 - Looking good regarding WASM crashes

[ksp100]

Hi,

It is easy for us all to flag things when they don't go right, but we don't always share positives. So, I just wanted to say I have now completed a couple of flights with v1.2.5 including a longer sector using time acceleration. I have repeatedly kept changing the arrival rwy/star during the flight to see if it breaks it but so far I have to say it is taking it in its stride.

Well done to the team.

Regards,

Kevin

[pvanderv]

Same here.

[klusik]

As soon as I get home from aero Friedrichshafen, I am updating and I must try! Thank you for a good vibes and message 🥹✈️❤️

[LineDX]

Thanks Team @iniBuilds for your continued effort upgrading this lovely aircraft. Glad to see it is flying in huge numbers on Vatsim CTP event. Keep up the good work team. 

[manfredfunco]

I started an overnight 8+ hr flight, one that has resulted in the ghost WASM freeze several times in the past and woke up to find the flight still ok and almost at TOD. I even had FSFO, FSUIPC, Sayintentions.ai, spad.next running which i would disable in the past to diagnose the wasm freeze issue  

The flight was fine but the A/T was disengaged so it wouldn't descend until I enabled it again. Not sure what happened there but great to see the flight was fine otherwise. 

Thanks iniBuilds for the update and the continued work on the A350. Will try a longer flight with time acceleration next. 

[manfredfunco]

I started another flight from RKSI to KDTW (1.2.5), no time acceleration yet. After 1.5 hours, I got the sim freeze. Plane still flying, displays/AP don't respond. I loaded the last autosave to resume, but this time removed FSUIPC, FSFO, GSX. Have SmartCARS, Sayintentions.ai, Navigraph Simlink running. Will report on how it goes.

Btw, before the previous flight (that worked), I uninstalled the A350 completely, re-installed, made sure the WASM folders were deleted, deleted rolling cache, etc.

[Kirkus]

8 hours ago, manfredfunco said:

I started another flight from RKSI to KDTW (1.2.5), no time acceleration yet. After 1.5 hours, I got the sim freeze. Plane still flying, displays/AP don't respond. I loaded the last autosave to resume, but this time removed FSUIPC, FSFO, GSX. Have SmartCARS, Sayintentions.ai, Navigraph Simlink running. Will report on how it goes.

Btw, before the previous flight (that worked), I uninstalled the A350 completely, re-installed, made sure the WASM folders were deleted, deleted rolling cache, etc.

Do you use noolaero VDGS?

[manfredfunco]

I do not use VDGS. When trying to avoid the sim freeze, I only have a few core addons enabled (sayintentions, navigraph simlink, spad.next).

Update on the last flight - after resuming, the sim was stable for many hours until I was being vectored to final. I used 2x accleration during cruise but back to 1x a few hours before TOD and for the rest of the flight.

When I was being vectored for final approach, i couldn't change the heading (sim freeze). I reloaded the last autosave point, was on final approach and couldn't disable the AP (sim freeze). After restoring I was able to land.

@iniBuilds I know sim freeze is different than a WASM crash and this is being looked into with Asobo. Is there any information I can collect for this? Or just be patient for a future update? I don't see anything of note in the dev console log. 

[IniJamir]

4 hours ago, manfredfunco said:

 I know sim freeze is different than a WASM crash and this is being looked into with Asobo. Is there any information I can collect for this? Or just be patient for a future update? I don't see anything of note in the dev console log. 

Unfortunately no. As you stated above this isn't a true WASM crash; which also makes it very difficult to reproduce or pinpoint, as it doesn’t trigger anything in the debugger.

Thank you.