sgb478

The original version of this aircraft, for me and my system, was the original version! I was flying all over the world. Then, iniBuilds issued two updates, and the issues presented in this thread started happening to me. How do I downgrade?

Hi richboy2307! Thank you so much for the explanation. In my particular case, I had issues mirroring ChristerH's that began after the updates. I bought the A340-300 that day it became available, and I actually downloaded it instead of streaming it. I was enjoying the A340-300 tremendously. Whether I was flying from KMDT to KCLT or KLAX to LIRF, the flights were unmatched. Then, I upgraded to version 2 and have had issues since - autopilot not engaging, nose-dive crashes in rare instances where the autopilot did engage; CTDs mid-flight, autoland ignoring the ILS signal. I wish I would get back to the original version.

I'm wondering if it's possible to downgrade from the A340-300 v2 to the first version? In the first version, I was happily flying all over the world - to any airport and from any airport. Plus, I experienced no CTDs. I was enjoying the flights. As soon as the Streamed Edition went to v2, however, I can no longer fly the 340. MSFS 2024 crashes to the desktop shortly after completing the cold and dark process, shortly after takeoff, during climbs, and during the approaches. Plus, the FD disengages every time I engage the autopilot, if the autopilot even engages. Finally, v2 no longer autolands, because it isn't picking up the ILS signal. I had none of these issues with the original version. To get MSFS 2024 functional again on my system, I installed a new SSD, reinstalled Windows 11 Home, reinstalled MSFS 2024, and I disabled the A340-300. Now I'm happily flying all over the world again. If I may ask, what changed so dramatically in v2? Thank you.

I was using iniBuilds' first edition of the 340-300 with no issues. Then, iniBuilds updated it, and my flights were over. Every time I tried to fly the update, MSFS 2024 would crash at either the gate, the taxi way, the run way, or mid flight. Then, I found your post, ChristerH, and my problem is solved!!! Thank you. Note to iniBuilds: After Version 2, I had to change all my graphics settings. The only one that solved the CTD problem was this solution.

Hello Eddie. Thanks for responding to my messages. I may have fixed my issue with Autopilot not engaging and disengaging as soon as it engages after take off from any airport other than KMDT. I followed these three steps to fix my issue. First, I "repaired" MSFS 2024. Then, I deleted the "rollingcache.ccc" file and increased the default size of 16gb to 32gb. Finally, I followed the A340 Manual to a "T," and that included setting the TRIM and pushing the "AP" button on the dashboard instead of the "Y" button on my HOTAS One. So far, I have successfully departed KSEA, KSFO, KLAX, and KSAN with no issues. Thanks again for responding to my initial and follow-up messages. sgb478.

I have double checked and no failures or assistance options are enabled. Every flight I try from KMDT is a successful flight, whether I start "cold and dark" or at a runway ready for departure. Attempted flights from KSEA, KSFO, KLAX, KSAN, KORD, KIND, KMCO, KCLT, EHAM (to name a few of the hundreds I have tried) have resulted in failed attempts. On these failed attempts, either the autopilot does not engage or it does engage and sends me crashing into the ground. i have no idea what I'm doing wrong at other airports...

Hey cinnamon21: How did you resolve that issue? I have the same issue. Original report: "When I start the aircraft in 'cold+dark', or 'on APU', I am unable to get the INOP SYS 'AP 1+2, CAT 2' message to go away."

My first flight after purchasing the A340 on 10/7/25 was from KMDT to KCLT. The aircraft and all it's systems worked perfectly. Since then, I've tried flying out of nearly 200 airports worldwide with the same result: "Inoperable Systems - AP1 & AP2." After taking off, I try to engage the autopilot, and it engages momentarily before disconnecting and crashing the aircraft directly into the ground. Upon restarting the flight, the AP is not available at all. So, I restart the sim, try flying out of KMDT, and the aircraft works perfectly. Why am I only able to fly out of KMDT with a flawless A340 but completely disfunctional everywhere else in the world?