leo5now

Aircraft: A350-900 Simulator: FS2024 Navdata Method: SIM DEFAULT OFP: KBOSLSZH_PDF_1766115354.pdf WASM Error: n/a Specs: Intel i7-9700, RTX3050 8G, 32GB Autosave File: 1766135472.bin

Now there's just more

I've got a bit of an interestingone. This isn't a WASM crash, but a WASM freeze. I didn't get the red displays when it crashed; the displays just froze. When I looked up on the console, I saw this message. I'm not entirely sure if this has to do with Inibuilds planes, but I had it 5 times in a row already on the A350 in testing.

To reproduce Selected changed from ILS to Visual Approach on the MFD, selected APPR first then it crashed Recommended to do the full flight because when loading the autosave, the WASM crash will not be replicated Aircraft: A350-900 Simulator: FS24 Navdata Method: NAVIGRAPH OFP: VHHH/25C DALOL1D DALOL V651 SABNO A583 AKOTA W3 IOO B472 GV DCT 16S139E 2025S14153E DCT LRE DCT 2557S14639E DCT SGE Y161 OVNOM H652 BOREE BOREE4A YSSY/34L Specs: Intel i7-9700, RTX3050, 32GB RAM Autosave: Attached latest .BIN file before crash WASM: WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty 1750767549.bin I gave everything pls inibuilds fix this 1750767549.bin

This wasn't really prevalent before, but it's happening now every time I change something on the A350 route in the sim, and it just has a stroke. Could it be one of the WASM issues or something else?

Well, it looks like my luck caught up to me, I had a WASM crash after 10 hrs of flying RKSI - KSFO, was planning for the arrival until Oakland recleared me to a visual. After changing from ILS to visual approach, the MFD froze and had a WASM crash, this is just insane now. Back to the drawing board, I guess...

I'd recommend reinstalling the aircraft fully and clearing out the WASM folder for those experiencing the WASM module crash. Before, when a WASM crash happened, for me, it wouldn't indicate the cause in the debug menu, which was weird. If you've verified that it's a WASM crash with the message in the debug menu, then try clearing out the WASM folder or reinstalling the plane if the problem persists. That's what Inibuilds always recommends to users

Hmm... i tried to disable the weather radar on the ND during mid-flight, but I still got a WASM crash. It wasn't until I realized that I had RT shadows on so I turned it off, and all of a sudden, there were no WASM crashes 😄

R u using SU3 Beta?

Hello! Thanks for responding to the thread! I think I'm calling it here that the weather radar or any additional information on the ND that constantly adds to the WASM module doesn't affect the WASM crashes. It had before in previous versions, like the glitch in which the TRAF radar on the ND would cause a WASM crash, but in this version, nothing. The flight I am testing right now, RJTT-LFPG, has also reached the 11-hour mark, so this is likely due to user error, where users may not have optimized their settings to account for Virtual Memory usage. VRAM is important, but VM reaching its limit is where the majority of the WASM crashes happen. I'd just recommend users keep an eye on their VM, leave about a 4-5 GB buffer during mid-flight, and then they should be good. FG is also fine, but just make sure it doesn't max out the VM or the VRAM. But feel free to test it out cause in my case, none of the systems here in the plane have any role in contributing to a WASM crash in V1.0.11 atm

just the WX on the ND both off on CAPT and FOs

Scenario 1: FG ON, RT SHADOWS OFF, W/X RADAR OFF and ARPT OFF - Completed no WASM crashes Testing soon same settings but with weather radar on and arpt on now to see if it will affect the flight also important to note that the OANS wasnt used in the departure airport so I will be doing a full typical setup on the A350, like what everyone does for a flight

Happy to report that the flight im doing right now (EFHK-RJTT) with RT SHADOWS OFF, TAA, NVIDIA FG, and W/X OFF/, ARPT off, has reached the 11- hour mark!! but then i realized i didnt have real world weather on...y is this not on by default

In the first test run - FG OFF, RT SHADOWS OFF, DLSS DLAA enabled, and WX off and ARPT off using the YSSY - KLAX route, I was able to push the plane up to 10 hours and then I had to leave it cause I had something in the morning so I wasn't able to land.

Yep will do! Actually majority of my WASM crashes do not show the error message in the module which is more complicated since idk if it's from ini or MSFS or just when you ran out of virtual memory.