That certainly should not be ruled out. I myself had orange screen wasm crashes across multiple airliners on just about every other (short) flight, often while sat at the gate before pushback and found it was FSUIPC that was triggering them. I’ve not had one (2 months now) since disabling FSUIPC. BUT I have only flown the A350 for 2 1/2 hrs not 11hrs and I rarely fly anything else from Ini, so I can’t categrocally say that they don’t have an issue. BUT it would definitely be worth disabling add ons and trying. Even if it is a spurious anomaly in the C++ code then it could be being triggered by exernal apps or mods. As far as I am aware this has only been happening since SU4 so there is that to think about too. I realise it’s not much fun flying vanilla sim to debug, but it may be worth a go.
The long flight wasm crash is reminding me of the long flight black screens that plagues XBox back in FS2020, when memory ran out.
I did not run into many “Orange” WASM crashes. They usually hit me when I am still at the gate.
What is plaguing me is the “no clue” WASM crashes, where all displays freeze, no controls and no switches work anymore but the plane keeps flying it’s current attitude.
Unfortunately I see those quite a lot on long flights.
I’d prefer to have the “orange” crashes at those instances, as I could immediately reload the autosave and continue.
The “no clue” WASM crashes goes unnoticed for quire some time and my carefully planned time window closes to finish the flight and I have to kill the sim without landing, having lost multiple hours of flight.
I don’t really see how it could be something else, as it is exactly the same behaviour as it was decrib3d as “WASM crash” before the introduction of the “orange screens” (i think with SU4 ?).
As I am not a developer I do not activate the developer mode.
But I frequent the support forums, and this behaviour (frozen displays) was always ide tidied as WASM crashes. So I have no reasons to believe that suddenly something else is happening..
I am pretty sure that a search on this forum will return many results that identify “frozen displays” as WASM crashes.
iniBuilds has asked for any users experience WASM crashes to A) verify this in the console, and B) submit specific sections of the console output to them for troubleshooting/debugging, so I wouldn’t say it’s a feature exclusive to developers.
I think it’s fair to say that while it may look like a WASM crash, I would always feel more comfortable with definitive proof - which is easily attainable. Without it, developers are potentially chasing the wrong issue.
Took the latest version of the A359 on an 8.5 hour flight from LVFR Miami KMIA to MK Studios Vantaa EFHK. Programmed the arrival during the cruise as it was an overnight flight with pause at top of descent enabled because I wasn’t getting up that early
On the ground in Miami, it was quite stuttery, especially compared to the PMDG 737 and 777 that I have been flying recently. Adjusting the altimeter at the gate was causing huge, several seconds long freezes. Taxi and takeoff roll were quite laggy but the rest of the flight went fine until I got a huge freeze at 100ft before landing on 22L at EFHK. Landed, stuttered it’s way down the runway and taxied to the gate. No orange screens or anything like that but wow does it still need some serious optimising. It’s not even like it’s got a cabin like the 777 does
Yeah this was in the 900. I was climbing out after takeoff and set my arrival. Then I realised I hadn’t picked an approach VIA so went back on to add it and immediately got orange screens. So wasn’t even close to my destination - had been in the air for less than 10 minutes
Also getting long freezes for lots of things on the ground. Changing altimeter, setting takeoff speeds, etc. Just shouldn’t be like this
I bought it and regret it…knew it was heavy on fps and was prone to WASM crashes and while it’s better in those 2 areas after the latest update, it still needs a strong pc and can have WASM crashes out of nowhere. Check the inibuilds forum and that’s a common post. It is great visually and has lots of complexity to learn with all of the cockpit glass screens. The other thing is that Winwing hardware isn’t compatible and I like using my physical hardware. The 350 has loads of touchscreens so it’s really for flying with the mouse. I also have the inibuilds a340 and that’s better on the fps, is more similar to the 320/330 in the ability to use physical hardware like Winwing, etc. and it has the vip variant which is cool to check out. I’ve found the a340 less prone to WASM crashes too.
i think we all were excited for a high level A350. our mistake probably was to belive the marketing speech. also here a bad purchase. maybe they get their stuff together in future but recently there were no further updates addressing the WASM or bad fps issues.
will not buy ini stuff again anytime soon.
I would recommend the in sim 330. To learn on it’s good enough and then make a choice whether you want to buy any other 3rd party. The 330 has some minor glitches and there are a few workarounds if you read the threads on it.
The A350 works extremely well on my system… WASM crashes have been rare and go back months ago - now it is quite a stable airframe tbh. I am surprised how many people are having issues with it. I by no means have a high end system and fly it in VR.
Agreed. They have made about 20 updates to the plane since release and it has been completely fine on my system since the 3rd or 4th update. Looks great and the integrations with Simbrief and GSX are best out there.
Take it for a long flight (5hrs or more) and start changing flight plan in MCDU (or whatever it’s called in A350) during descend. This is when most WASM crashes happen. I didn’t experience any WASM crashes for 4 months and then decided to try the longest commercial flight WSSS-KJFK. When ATC gave me a different landing runway to what I had pre-planned I knew it won’t end well. I was not even mad when all screens turned orange during approach :).