D Dragon

I was having a pretty rough time with MSFS 2024 SU3 beta over the last few weeks struggling to figure out why I was constantly experiencing poor framerates and CTDs every time I got to the approach phase of my flights... at first I thought it was related to some WASM issue with the A350, but soon found that it occurred regardless of the plane I was flying. I tried correlating the behavior to 3rd party tools like BATC, GSX, Navigraph, etc, but regardless of what I disabled I was still experiencing crashes. I was almost ready to give up on SU3, but after updating my video driver (Nvidia), and deleting / rebuilding my rolling cache file, the CTDs ceased, and as a bonus everything, including the A350, is running markedly better. At least on my system now the A350 is absolutely lovely to fly. I know this is not a guaranteed fix for all CTD issues, but at least in my case it was definitely the cure.

Thank you! I believe this is a GSX Pro issue, as I am seeing similar behavior with GSX interactions with other aircraft as well. It seems to affect aircraft loading operations (fuel, passengers) particularly. I tested GSX pushback with the A350 and that at least worked without issues.

I just updated to the v1.0.11 A350 version, and in SU3 beta if I choose any GSX Pro (latest GSX release as of 5/31/2025) service I get an immediate CTD. In SU2 I don't get a CTD, but I get lots of aircraft bouncing if I use GSX refueling or passenger loading services. It appears the 1.0.11 A350 build and GSX Pro do not get along.

From the above thread, Inibuilds confirmed that TCAS is a known issue right now and they recommend not enabling it: "We have identified something similar and working on a fix already; so yes, avoid TCAS for the time being 😉"

For reference, I have been flying the v1.02 A350 without any significant issues (other than pilot error) since it was released, and I am cursed with some of the weirdest bugs in MSFS 2024. I would recommend the following to give the A350 the best chance of working: Use the MSFS 2024 beta build even after the release of SU1 - it's probably a good idea to stick with the beta build at least through SU2, as there are still numerous issues with the sim at this point. Completely delete the A350 WASM folder contents - this is critical. Update to V1.02 only after you have deleted the WASM folder contents. Do an initial instantiation of the aircraft on a runway and let the aircraft systems initialize before ending the flight (or just take off - hey, you're already on the runway!) Hopefully these steps will make the plane flyable for you - I feel like if it can work on my very problematic MSFS 2024 install, it can probably work anywhere.

I have noticed that since the latest MSFS 2024 SU1 beta update (on 2/13) the aircraft systems will randomly reboot and go into an unstable state, with odd behavior such as rapidly cycling pack valves or resetting fuel levels. The aircraft will go from completely normal configuration with no issues to the avionics power cycling followed by random instabilities and an unusable aircraft configuration. This has happened on 4 flight attempts since the latest SU1 update. I have tried clearing the MSFS 2024 cache as well as clearing / resetting the aircraft WASM files, but the behavior has persisted.

I would check to see if your TOGA button on the Airbus TQ is explicitly mapped to TO GA in the msfs controller settings. You can just go to settings -> controls -> Airbus TQ and do a search by input - press your TOGA button and see if TO GA is mapped to it.

That worked - setting the ignition to off fixed the depressurization at altitude - thank you for the guidance! And yes, I figured out the altitude performance as well. Thank you again!

I have noticed on my past few flights that I am consistently getting a cabin pressurization failure above FL300 (more or less). At lower altitudes the pressurization functions, though it does not seem to pressurize the cabin at an expected value - the cabin altitude seems to be higher than expected at a given altitude, and the cabin pressure altitude discrepancy increases as the aircraft altitude increases. At altitudes above FL300, the pressurization eventually just gives up and the cabin depressurizes completely. Am I missing some pressurization procedure setup prior to takeoff? The pressurization system seems to default to auto settings initially, so I do not change them. Also, the FMC gives a cruise altitude above max flight level message at FL360 - isn't the A300 rated to FL400 for cruise?