manfredfunco

After updating to SU5, I able to complete a flight from EHAM to KATL (8:40 block time) with no freezes (no FSUIPC, no GSX). Sim was stable the entire flight. I don't know how much of this is because of SU5.

Thanks for the tip on enabling Simconnect logging. I'll check it out. I was previously looking for Simconnect spamming from the menu items in developer tools and didn't see a lot of activity there but will try the logging and report if I find anything.

Sorry, but welcome to the freeze club. What other addons do you have running? Do you have FSUIPC installed? What throttle/stick are you using?

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.

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.

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.

That's great to hear you may have an upcoming fix for the "Ghost WASM" issue! I have a long-haul flight I've stubbornly attempted many, many times (KDTW - RKSI, without FSUIPC, using SmartCARS), which always end up in this state (plane keeps moving, but avionics are frozen, can't control the plane). I usually use a lot of addons but attempted a barebones flight overnight with just FSUIPC + A Pilot Life. I hear FSUIPC alone may cause the issue but needed it for tracking the last particular test flight (KORD to LIRF). These are the addons/apps that I regularly use but completely disabled / did not open / removed from community folder for the A350 tests. The last flight was just FSUIPC + APL and still resulted in the Ghost WASM issue. Clear WASM cache before flight - after installing v1.2.4 Making sure Sayintentions/Hoppie IDs are not entered in the OIS. Used the No Cabin Version Used Delta Livery from the iniBuilds app. Removed all other liveries/addons from community folder Verified during the entire flight, my GPU (RTX 3080, 10GB) VRAM was < 70% Process Lasso Chaseplane 2024 Flow SayIntentions.ai Navigraph Simlink (known culprit) Spad.next Moza Cockpit (for MTQ, AB9) FSFO 6 Disabled Photogrammetry, All traffic. Used MSFS Sim Real Time/Weather Windows Apps Disabled all Bitdefender protections, other than the Firewall Made sure Powertoys is not running Killed unnecessary Windows Services Kill all other background apps - Browsers, Discord, etc. Let me know if any more information (or tests) from me could help you troubleshoot the Ghost WASM issue. When I experience the freeze, I check the console, Simconnect Inspector and don't see any relevant WASM errors or "noisy" simconnect apps. I was considering writing a program next to check for the ghost WASM issue (checking if certain Simvars are no longer changing) and automate pausing the sim, send me a notification. Then I could restart the flight w/ Autosave to resume. Sounds like I can just wait for the update! Thanks!