Strange thing happening here.

 

I've only done 2 flights so far, but both have had the same issue, about 1-2hrs after departure in the cruise, I notice all of a sudden that the MCDU's are frozen with no way to input or change anything, the aircraft also locks me out of changing any autopilot inputs and goes into what I assume must be heading hold, as it drifts off the track in a straight line for eternity. Not sure if anyone else is having this issue or not, but I'm concerned to see it twice in a row on my first two flight attempts!

Happened to me while still sitting on the apron. I was going through preflight and MCDU simply stopped responding.

10 hours ago, Mantock said:

Strange thing happening here.

 

I've only done 2 flights so far, but both have had the same issue, about 1-2hrs after departure in the cruise, I notice all of a sudden that the MCDU's are frozen with no way to input or change anything, the aircraft also locks me out of changing any autopilot inputs and goes into what I assume must be heading hold, as it drifts off the track in a straight line for eternity. Not sure if anyone else is having this issue or not, but I'm concerned to see it twice in a row on my first two flight attempts!

I've had this happen twice so far - seems after setting the autopilot after a little bit everything freezes - aircraft flies straight - doesn't follow the flight path - the buttons become non-pressable (can't turn off the autopilot or set or change anything - everything seems to freeze up and have to restart the flight.  Have updated the navdata a couple times....not sure what's causing the freeze other than maybe my rig running out of ram?  

it can't be running out of ram. I hope we get some idea, because none of the streamers i have seen have run into this, and nobody seems to be talking about it

Ok, my third flight attempt, I've completely turned off the gsx synchronisation features in the efb, and immediately the nose wheel steering works AS IT SHOULD. So thats a step forward, once I'm in cruise I'll see if the AP/ND freeze issue is still present

Nope! same exact thing happened, about an hour and a half into the flight, the navigation completely locks up, ND range doesn't work, FMC doesn't respond, AP inop. For goodness sake Inibuilds, how do you have a product where all the streamers have zero issues, making the product look good, and when you throw £56 at a product it doesn't even work properly. 

 

I'm not new to Airbusses either. If I can't complete a flight after three attempts, what's the use? If whatever this is isn't patched asap (so that I can actually use the product) I'll be pushing for a full refund.

I realised my GSX wasn't fully updated to the newest version, so I have updated that and will try again tomorrow. If that doesn't work I'll keep reporting until I hear how it can be fixed, or what it is that I'm conceivably doing wrong. 

Edited October 11, 2025Oct 11 by Mantock

It happened to me, flying to Australia, after hours of flying, the aircraft simply froze and went off, made a turn and apparently was returning to the departure airport, but I couldn't control anything anymore.

 

Ok, so my third flight is the first successful flight ive done so far. This time around I didn't touch GSX at all, and I wonder if thats what the issue was?

 

EDIT

 

But then, on my fourth flight attempt just now, the MCDU's froze up as I was initialising my route while on the stand! I had opened the gsx menu from the tab at the top of the screen, but not clicked any buttons.

Edited October 12, 2025Oct 12 by Mantock

I am having the same issue, however I realised that the only flight I was able to complete was my first flight when I forgot to download updated Airac.

@Mantock @Freitas138 @pappa_razzi @Jure are all of you flying with Navigraph AIRAC installed? Try with default sim... I dont have time to check this myself as I already spent my entire weekend trying to sort this out (great use of my time btw thanks iniBuilds). 

2 hours ago, Roders said:

@Mantock @Freitas138 @pappa_razzi @Jure are all of you flying with Navigraph AIRAC installed? Try with default sim... I dont have time to check this myself as I already spent my entire weekend trying to sort this out (great use of my time btw thanks iniBuilds). 

Yes, my flight with the MCDU freeze was with updated Navigraph AIRAC. After a couple of days I decided to try again, deleted the WASM A340 folder and forgot to update the AIRAC. My EDDF-LGAV flight went without a hitch. Now, the question is, where is Navigraph AIRAC installed? Did I fly with the updated one or not? I did notice that A340 STARS were not exactly the same as in BATC and LittleNavMap. You could be on to something here, Roders...

6 hours ago, Roders said:

I am having the same issue, however I realised that the only flight I was able to complete was my first flight when I forgot to download updated Airac.

@Mantock @Freitas138 @pappa_razzi @Jure are all of you flying with Navigraph AIRAC installed? Try with default sim... I dont have time to check this myself as I already spent my entire weekend trying to sort this out (great use of my time btw thanks iniBuilds). 

Can confrim as well. Default Navadata no issues. Latest AIRAC through Navigraph gives me WASM crash after about 3 hours of flight. 

4 minutes ago, vumi101 said:

Can confrim as well. Default Navadata no issues. Latest AIRAC through Navigraph gives me WASM crash after about 3 hours of flight. 

Yeah my WASM crashes were happening c. 30-60 mins after departure, so a bit earlier, but also only with latest Navigraph AIRAC. Might be worth changing the title of this topic to better reflect the Navdata issue. Hoepfully ini see this.

Because its a market place release, update could take weeks or even months - might have to shelf this aircraft as flying on Vatsim without updated AIRAC data is a bit tricky. Shame as the A343 is by far my favourite AC out there. 

Hello,

First of all, apologies for the inconvenience. We hate these WASM crashes as much as you all do, if not more.
We've created a guide on how to report said crashes. This makes it a lot easier for us to identify the issue. Please create separate threads with the necessary information. 

It may also be worth using the autosave feature we built to no longer need to scrap an entire flight. Restarting the simulator then loading an autosave file to keep going from the same point you left off from - should take max 10 minutes depending on your simulator load-times. A guide on how to use this feature can be found here: 

Thank you 🙂

Sorry I didn't get the wasm crash console stuff, next time I have this happen I will make sure to remember to do that! Here is another longhaul attempt

Well, it's the same for me.
After about 2 hours of flying, all the buttons froze, impossible to regain control. I tried 3 times to fly from EDDF to KDTW and the same thing happened each time.
It's annoying when, like me, you're building a career on PilotLife and have to start over.
With all these bugs on the A350 and A340, I lost 3% of my XP level.

So i started a flight this morning after the 1.0.1 update, and sure enough, same issue happened, I checked the console but have NO errors, only a few warnings which I show in the screenshot. Same issue, MCDU froze, not able to change pages, ND range selector knob turns but the ND range doesn't change, and the aircraft stops following the nav path and just goes off on its own little ramble across the sky

Edited October 17, 2025Oct 17 by Mantock

Are you all on SU3 or SU4? 

SU3

Just had the same thing in SU3, so frustrating man. @iniBuilds Do you guys have any hints as to what this might be? Just a bit of info would be great, with the recent update and general praise for the aircraft a lot of us feel abandoned here.

Console errors/warnings near the time of the system freeze are below, I have also attached a .bin file.

1760867410.bin

Edited October 19, 2025Oct 19 by Roders

I'm finding that pretty much every other flight this crash happens and I loose the flight. Some flights are perfect and the plane operates as it should and its great. And then all of a sudden, wham, it happens again and another longhaul attempt is lost

SU3

SU3
On Saturday, I disabled the A340 in my library and downloaded version 1.0.1, and I was able to make two flights without any problems.

Mais uma informação

SU3
 

• Aeronave : A340 EIS2 Passageiros
• Simulador : FS2024
• Método Navdata : NAVIGRAPH
• OFP:  SBKP/SAZS
• Especificações:  Intel I9 9900K, RTX 4070, 40 GB de RAM
• WASM: nenhum apareceu na lista

 

1760979117.bin

Edited October 20, 2025Oct 20 by Freitas138

had the issue again yesterday on v1.0.2

 

I'm still running SU3.

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?