AVGA

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.

I have to do this after every GSX update, or seated passengers won't appear in the Fenix. Still can't get seated passengers to work in the A350 though. Really wish I knew why, as I don't think I'm missing a step or anything.

Downloaded latest update. Set up a new flight. Got to 10000 feet and then sound cut out, came back, and MSFS2024 completely froze. Error log is attached. Please also note the lengthy amount of fuel system errors. Not sure if that's the reason for the freeze, but there sure is a lot of them. Thx.

Thx. Am familiar with all of that, but nothing explains why passengers aren’t properly boarding, seating, and in place throughout flight. For the Fenix, you have to check and uncheck the seated passengers box in the installer after every GSX update (a long time known bug), so even tried same for A350 - which also appears on the seated passengers list - but it didn’t resolve the issue.

Hi, GSX Pro claim to now support all variants of the A350 with seated passengers, but mine disappear at takeoff ... then reappear at landing. Is this intentional -- to preserve frame rate or stability -- or am I missing something? I have the latest version of GSX Pro, and the A350, and have also ensured that all A350 options are checked within GXS Pro's installer. Any help would be appreciated. Thx. Len

I would, but as my problem was a complete system freeze, there was no ability to get back to the main menu to look up the error. Had to force quit the sim, and upon reopening the program and going straight to the dev console, nothing was logged. Nor was anything found in Event Viewer. So, there is no information to me to provide, other than: - The freeze happened while trying to manually adjust vertical speed - Just before this, I briefly activated WX, which I never usually do, since there had been prior reports of WX use causing WASM crashes, but thought perhaps this was now fixed - along with Navigraph use causing WASM crashes

Was happening to me all the time, then the latest Inibuiilds update appeared to solve it ... until yesterday, when 2 hours into a 4 hour flight, I went to change altitude and got a total system freeze. Nothing logged in Event Viewer, and since the sim froze, force quitting and then going back into MSFS24 resulted in nothing showing in the sim error log, either. Assuming it's yet another WASM crash, but can't verify. Totally agree about stress ... every flight with this plane is a nail biting "will it CTD" experience. Which is such a shame, as the plane itself is incredible. Judging by their recent replies, Inibuiilds seems to be getting fed up with the requests to fix this, but something needs to be done, as we aren't the only ones having a problem, and it's definitely not my PC.

Same issue here. Also en route to VHHH, oddly enough. And it happened just a minute after I stupidly activated the WX, thinking it might be safe to use now. So, wondering if this is the same WX WASM issue as before, or if it's just a coincidence.

Have had the same issue since two updates ago. Same type of freezing, and no errors reported in Windows or MSFS24. As much as I enjoy the A350, I’ve given up on this plane until this is fixed. And yeah, I’ve tried everything Inibuilds and others have suggested. It’s a software issue that needs to be addressed.

Hi, Thank you. I’ve tried not using Navigraph data in the OIS, not using the OIS map, not using WX, and not using terrain - all of which was suggested to me. I’ve also cleared the WASM folder. But every flight freezes at some point … only since the last update. Can happen any time, though so far not while on the ground. Cockpit just freezes while sound continues to play, along with SayIntentions, which isn’t affected. Also, the sim doesn’t CTD. It just seizes up, and I have to force quit it to return to desktop. But PC is fine, as in, clicking off the sim is fine. And there is nothing reported in event viewer. welcome your thoughts. Also, can you confirm how to resume an auto save? Tried to restore a frozen flight - from the ground by getting back into A350 and selecting the last save from the OIS menu - and I ended up back in the saved flight with a cold and dark airplane, leading to a flight crash that went on loop until I quit the sim.

All I get are freezes and CTDs since the last update. Did everything that everyone has suggested - including on this thread - and plane remains impossible to use since last update. And this is the only plane that does it. Fenix will go around the world without a single issue. Inibuilds can’t get to level cruise without crashing out, since the last update. Wtf.

Did everything you suggested and froze again - during the climb. Not sure what else to do, as this plane is now impossible for me to fly, and I honestly can’t figure out why. Not even an entry in event viewer … sim just freezes. And it doesn’t with any other aircraft.

Thanks very much. Am on SU2, but was using everything else you mentioned. Will try this asap and let you know. Thx again.

Hi, 4 hours into a 5 hour flight, during decent at 23,000 ft., all glass cockpit instruments froze -- speed, altitude, etc. -- and certain buttons stopped responding, along with all flight controls. Plane continued to fly, but proceeding was useless, so I was able to hit ESC to return to main menu. But the flight was ruined, also because when I restarted flight on the ground and hit autosave, I ended up back at cruise altitude, with a cold and dark aircraft plummeting to the ground. Followed by a "you crashed" MSFS loop. Has anyone experienced frozen instruments since the last update? This is a whole new one for me, and nothing is logged in the Event Viewer. Any advice on how to properly activate an autosave would also be greatly appreciated. Thank you. Len

Thanks. I didn’t see the larger thread about this at first, but will try the nav data change and see if that works as a stop gap.

Also got a coherentUIGT error my first time out with the latest update. Hadn’t happened with prior versions, so didn’t know about the nav data workaround. Will try it, but the bug is definitely not fixed with the update.

Checking the forum, we aren’t alone with these issues, though I’m most curious about others having the same error I posted here. Did you check to see if you could find any error codes specific to your problem?