Nace42

Aircraft: A350-900 (non cabin) Simulator: FS24 Navdata Method: NONE Specs: Ryzen 7 9800X3D, NVIDIA RTX 5080 16G, 64GB RAM Autosave: NONE WASM: Error during Systems_gauge_update execution. Error code : 0xc0000005 simple a to b with a direct too from OMDB to OEJN. traffic off, weather radar on (no idea why theres legs being loaded here tbh...prob the oddest wasm crash too. much further in a flight then normal for me. usually average is around the 35min mark is when wasm seems to fail for me). as always, was tabbed out while in flight, tabbed back in after a pre determined amount of time to a wasm crash.

Aircraft: A350-900 (non cabin) Simulator: FS24 Navdata Method: NONE Specs: Ryzen 7 9800X3D, NVIDIA RTX 5080 16G, 64GB RAM Autosave: NONE WASM: Error during Systems_gauge_update execution. Error code : 0xc0000005 ran into it when doing RJTT-RKSI (nothing but a direct too from RJTT to RKSI), tabbed out to read some stuff and walk away for a min, came back into the sim to screens frozen etc.

i actually enjoy it very much even with the issues honestly. its a really great aircraft and really easy on the eyes as well as photogenic, but thanks for the insight! always appreciate the extra info. fingers crossed things settle down regarding the wasm issue but regardless i am quite happy with the aircraft in the times ive been able to fly it etc. ill make sure to start posting every single one with whats needed from my side in the hopes we can crush these.

for context in the month its been out, the A350 has behaved the exact same as my previous pc build i had (R7 7700, 4060,32g of RAM), as it does on my new build (R7 9800X3D, 5080,64gbs of RAM) and also seems to happen on almost all the same routes (i dont dare try other routes outside of the u.s very often). are we sure we cant replicate these? i get one every couple hours of flying extremely consistently regardless of my pc build (for giggles ill boot up the old I7 2070super build and see as wel)l. dont take this the wrong way, i LOVE the A350. i just think some of us are passionate about wanting to fly this without having to reset WASM or whatever other tricks others use to get it to run right. the other day (last time i flew it) i reported a wasm crash for 24, deleted the wasm etc, reinstalled everything, and i ended up getting one abck to back in the same spot. i could prob fill up quite abit of the forum on the amount of wasm crashes i run into regardless of pc build. again i love the A350. im just providing more input and context regarding different issues on different systems.

a simple A to B direct too has about a 50/50 shot of working currently. ive ran into this so many times ive just decided to move on. even worse, ive had it to where a route would work one time, but then on the way back after closing the sim and restarting it, would cause a wasm failure. its the same route, but in reverse.....and all it is is a departure airport and a arrival airport plugged into the FMS. its quite disappointing for sure.

Aircraft: A350-900 (non cabin) Simulator: FS24 Navdata Method: NONE Specs: Ryzen 7 9800X3D, NVIDIA RTX 5080 16G, 64GB RAM Autosave: NONE WASM: Error during Systems_gauge_update execution. Error code : 0xc0000005 here i am again with another wasm crash, in v 1.07. doing a simple A to B direct to (EGLL-LICJ). are we any closer to solving these? ive only been able to do MAYBE 8 flights before i eventually reach a wasm crash thus needing to delete the wasm folder, which causes me to lose my maintenance stats etc. one of these day i suppose ill actually be able to use the "refill engine oil" button naturally. the amount of these i run into from a lower end build, to the best available is quite abit. USUALLY in places i dont normally fly. if i stick to my normal routes, i have 0 issues. tis odd. i only ever fly the plain white base livery thats given to us.

it acts like a walkaround item, pitot tubes and covers need to be clicked off before going into the aircraft (need to be outside the aircraft and click on them manually)

Aircraft: A350-900 (non cabin) Simulator: FS24 Navdata Method: NONE OFP: VTBS direct to WMKK Specs: AMD Ryzen 7 9800X3D / RTX5080 / Windows 11 PRO (up to date) WASM: WASM: Error during Systems_gauge_update execution. Error code : 0xc0000005 seems like im back to running into these again on build 1.06.....nothing fancy just a point to point (direct to), no navigraph or 3rd party plugins. started fine, took off tabbed out to check on stuff only to tab back in to it all frozen and not responding

yep im back to getting dirty wasm modules. the same nasty 0005 gauge error.....

you can manually set camera zoom in the sim options. i set my camera view to 0 normally, for this ive set it to 13 which isnt too close for me, and its fine.

this is related to your camera zoom. if you scroll wheel in a little, itll go away. this is reported on their discord and i have the same problem. my solution was to go into the camera settings and zoom in a little and wallah solved the flickering in the cockpit

more context, this is what it looks like in the white inibuilds livery on a fresh wasm clear, and reinstall. it seems initially it loads in fine, and then for whatever reason it changes over to the borked version late edit: saw this was logged on the ini discord. is related to zoom levels in the camera setting Untitled video.mp4

all liveries are doing this to me currently. any help would be great. for the 4th try, i uninstalled the plane via inimanager, uninstalled the game and then reinstalled both to get the same result. idk how things keep getting worse for me, as it seems nobody else has reported this or has an issue. (note that we do see inside another aircraft, i had just reinstalled the game and didnt change a single setting when spawning in and an AI aircraft was at the same gate) Untitled video (1).mp4

so updated the A350 this mornign and was welcomed to this in both the plain white base livery and the ini base livery. any ideas as to whats going on? the first try it was just an update over the existing and a wasm cache clear got this same result. second time i uninstalled via the ini manager, and cleared my wasm folder and got the same exact result. the third time, ive manually deleted it out of my community folder in msfs24, cleared the wasm folder for the 3rd time in the 3rd try, and got this same result again. am i the only one getting this??????? the entire cockpit is in this dark grey, and the OIS is on but the screen is flickering. i have 0 WASM errors in the debug menu (whats going on is that the entire cockpit is missing a layer or something is up. all the buttons on the overhead are glowing blue all at once, and the OIS is auto on without any battery etc, but flickering black) Untitled video.mp4

further errors im getting as well on current build 1.0.3

Aircraft: A350-900 (no cabin white livery) Simulator: FS24 Navdata Method: NONE OFP: EDDM-EGCC Specs: R7 5700, RTX 4060 Ti , 32GB RAM WASM: Varget of NAV HAS TACAN in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm failed with error 0xffffffff for further context, i have not been able to lift off and fly more then 25minutes since this last update (1.0.3). immediately upon spawning i get this wasm error and then shortly after liftoff, the whole wasm crashes the rest of the way making it useless (MFD_gauge_draw execution. Error code : 0xc0000005). i was able to get multiple flights done last night in the U.S but not in south america or at my current location (eddm) which makes things ever more odd.... im not doing anything fancy, simply typing in my departure and arrival with a direct to (just a simple A to B nothing fancy). as far as AP setup, manual heading mode, and simple AT again nothing fancy. ive done fresh sim installs, cleared every wasm and cache folder known to man all of which multiple times.

im getting more crashes with the current version of the A350 (1.0.3) and 24H2 then i have ever before. the most solid build for me was the first release build. since ive gotten non stop wasm errors all the same faulting module (systems_gauge_update). ive done several game reinstalls, aircraft reinstalls. whats odd to me is that no matter how many times ive done this, it STILL remembers my A350 settings (external config, dirt etc but NOT maintenance stuff altho for some reason i always have lower then full hydraulic fluid)). i wonder if us clearing the wasm isnt actually clearing it all out. something is obviously saving and remembering what external/cockpit config i had as well as wear and tear and sounds.

another morning, another flight ending in 20mins. yep it just hates me. i managed to do 2 flights last night no issues after my reports, wake up this morning and get hit with this again. all im doing is loading into an airport, and turning the aircraft on and taking off. im not using any WX/terrain/TCAS etc, not even using navigraph and simply running a basic manual heading and AT AP setup, tabbing out and my screens freeze. the flights i got done last night that i mentioned above, i never tabbed out of the game to check anything.

cleared wasm, uninstalled, reinstalled loaded in a flight and every time i tab out of the game for longer then a min im greeted to this (yes it just happened again after just reporting this. im convinced it just hates me...)

sigh the wasm crashes seem to have been worse. no TCAS no radar not using navigraph and in a simple cruise above the ocean heading to Argentina and got the MFD_gauge_draw execution. Error code : 0xc0000005. 2 times in the last 30mins its happened to me. both fresh installs. was able to fly with no issues last night so whatever it is, isnt consistent but seems to be the same faulting module. out of the main release and the two updates, this update has been abit worse as far as wasm crashes. the original release was perfect for me at that time.

i get it too. ive also noticed that it does this when my CPU spikes which also correlates to when i load in the next LOD chunk of the earth in sim. the only way ive found to make it better, is by dropping my terrain lod to 200 and lower to reduce the stress of loading in the terrain via streaming, while flying the A350. its very odd....

disregard above msg by me. seemed to have been the multiplayer servers causing the random stutters on the test of 1.01. all is well on my end.

stutters still remain after 1.01 update.

i have the same issue. i did a 3 hour flight and it occurred at random times throughout the entire flight (this was on a stream with 3 total B2's flying together in formation). i turned some screens off and it made it a little less impactful but the random stutters were still there. still a great aircraft, just need to sort out the stutters and whats causing them.