AVGA

Will do. Thank you.

Turned pitot and window heat on for a flight from Minneapolis to Toronto -- even though according to Airbus, it's supposed to be automatic (no need to activate it) -- and again crashed on final, in cold but not even icy conditions. Soon as I got to 2500 feet at flaps 2, speed tape went haywire, stall was announced, and plane dropped to ground. Will try again, this time with MSFS 2024 icing set to off, but am also doing a clean uninstall/reinstall, in case this isn't an icing thing. Really wondering if I'm alone with this bug. Thx.

Happened to me after last update, and fresh deinstall/reinstall solved it. Did same for latest update, and this bug is back. What gives?

Just flew from Newark to Minneapolis ... all perfectly fine until below 10000, then all hell broke loose. Got icing warning, turned on de icing systems, and plane went haywire. Automated systems failed, speed tape showed stalling at 220 kt, and plane wanted to plunge. Had to manually recover and barely made it to runway. Is this the icing bug in action? Never experienced anything like it before. Fenix does NOT do this. 🙂

A deinstall and reinstall was the only way to fix this issue, for me, anyway. Also took care of odd, possibly broken, sound effects that happened after the initial upgrade.

A fresh reinstall appears to have solved the issue.

Downloaded the latest update, plus a WASM folder clear out, and on first flight, landing gear wouldn’t go up. Lever moved into up position but gear wouldn’t move. Used the emergency gravity lever and that somehow fixed the issue. Is this a known bug with the update, or is it a possible update error … should I delete and reinstall the latest version? Thx.

Thanks very much. It matches mine, so at least I can confirm that GSX correctly includes the model(s). Thank you again.

Thanks. Can wait until tomorrow, unless there's an easy way for me to privately contact you to provide my e-mail or other contact info. Not sure how to go about that on this forum. Appreciate your help.

Thx for posting this.

Thx. I did do this, but without closing the Config menu and returning to it 1 - as simply unchecking and re-checking the boxes at the same time works for the Fenix. But I’ll try it as you described. Also would greatly appreciate a quick view of your seated passengers (config) menu in GSX. Thx.

It’s a post to see if anyone else is having a similar issue since the last update, and if so, perhaps some additional info or insight on it. Also submitted a ticket, but no harm asking for … what’s this forum called? Oh yeah. Support. If you’re not having the issue, and nothing to say about it, then move on. Plenty of other posts to entertain you.

Thanks. Am aware of how it works. Problem is that once they walk in, they disappear. Passengers do not go into cabin, or sit down. For de-boarding, they appear again when it's time to walk off. Entirely consistent with sequence when seated passengers isn't selected. So, I am assuming that seated passengers is somehow turned off, or there is a disconnect between the A350 and GSX somehow. If you wouldn't mind, could you tell me what options are present on your GSX Installer Config page -- in the "seated passengers" box at the lower right? I am wondering if the right option isn't present for me, and would greatly appreciate the help. Thank you again. Len

Yep. Did all of that, and still have a freeze issue, which is why I posted. I also never called it a WASM crash (on purpose), and posted the sim error log. Would also post the report from Event Viewer, and can do so on request, but to my eye, it’s not specific enough to be helpful. What I’m looking for is actionable insight and advice, not “empty your community folder” and other basic steps I’ve already done. Also did not post a rant, only a request for any help that can be offered, as while I really like the A350, the various crashes and conflicts I continue to experience make it a real pain in the neck - especially compared to Fenix and others who provide strong reliability out of the box. If Inibuilds wants to charge the same price, they’ve got to be more stable and consistent.

Go to Advanced Options in MSFS and choose developer mode. That will give you access to logs. This plane is always one step forward/two steps back for some reason. Works fine for a while, then there’s an update, then it fails again. So inconsistent.