46 minutes ago, jcomm said:

Well,

just a short followup... My LPPT - LPMA, Pax, EIS1 model flight froze exactly around 1 hr after having started 😞 when I was about to enter the STAR for LPMA 😞

I first tthought I might had inadvertently left the Pause before TOD enabled, but it wasn't, and there was no way to "unpause" the sim... But ESC allowed to leave the flight to the MSFS 2024 Main menu...

So, after ESC, you could not resume the flight...I understand...?

MSFS sometimes goes to sleep...on long-haul, if left un-attended. Usually, you can un-pause and resume your flight, but occasionally, MSFS would have gleefully closed everything out, for you to have to start a brand-new flight...

Did you see any "Memory Degradation" type message, or/and the dreaded "WASM Orange Screens"...I'm guessing not ...

Edited January 25Jan 25 by P_7878

39 minutes ago, jcomm said:

Well,

just a short followup... My LPPT - LPMA, Pax, EIS1 model flight froze exactly around 1 hr after having started 😞 when I was about to enter the STAR for LPMA 😞

I first tthought I might had inadvertently left the Pause before TOD enabled, but it wasn't, and there was no way to "unpause" the sim... But ESC allowed to leave the flight to the MSFS 2024 Main menu...

I just completed a flight in the A340 from YMML to YPPH all went well. No issues, but I entered my entire flight plan while sitting on ground at departure airport. I never tried entering star while enroute.

3 minutes ago, Bigmack said:

I just completed a flight in the A340 from YMML to YPPH all went well. No issues, but I entered my entire flight plan while sitting on ground at departure airport. I never tried entering star while enroute.

Nice.

Yes, I recall, some reporting of crash/CTD while adjusting FMS Route entries in mid-flight, such as entering or/and revising STAR, but not in my experience of the A343 ...

9 hours ago, Bigmack said:

I just completed a flight in the A340 from YMML to YPPH all went well. No issues, but I entered my entire flight plan while sitting on ground at departure airport. I never tried entering star while enroute.

I didn't either... BATC had just assigned me a STAR and  I was about to open the MCDU when I noticed the aircraft "was frozen" 😕

Edited January 26Jan 26 by jcomm

11 hours ago, P_7878 said:

So, after ESC, you could not resume the flight...I understand...?

MSFS sometimes goes to sleep...on long-haul, if left un-attended. Usually, you can un-pause and resume your flight, but occasionally, MSFS would have gleefully closed everything out, for you to have to start a brand-new flight...

Did you see any "Memory Degradation" type message, or/and the dreaded "WASM Orange Screens"...I'm guessing not ...

Yep, on other rare MSFS crashes (mostly in FS2020 times) I was forced to do a hard reset to leave the simulator process ... Not this one, and that's why I even thought it might have been the "Pause before TOD", but it wasn't.

Nothing worked in the aircraft, not only the MCDU, also the FCU the throttles the spoillers, overhead panel interaction... Nada!

Edited January 26Jan 26 by jcomm

6 minutes ago, jcomm said:

Yep, on other rare MSFS crashes (mostly in FS2020 times) I was forced to do a hard reset to leave the simulator process ... Not this one, and that's why I even thouht it might have been the Pause before TOD, but it wasn't.

Nothing worked in the aircraft, not only the MCDU, also the FCU the throttles the spoillers, overhead panel interaction... Nada!

I have had the same on what was to be a 7hour flight from the KEWR-EGLL, as you say nothing works when the error occurs. Only a hard reset solves the issue. I just stopped using it since it had occurred to me a couple of times, and ended up not using the aircraft since. I may try it again today to see whether it's still the same.

Edited January 26Jan 26 by Simselli

On 1/25/2026 at 11:36 AM, pmplayer said:

This WASM issues are a inibuild thing, happens to all planes they released, needs about 20 updates, at least this was the case with the last planes so seems a bit more time until all is fixed..

cheers 😉

well if you head over to the pmdg forums users are now having  these wasm crashes as well

6 hours ago, jcomm said:

Yep, on other rare MSFS crashes (mostly in FS2020 times) I was forced to do a hard reset to leave the simulator process ... Not this one, and that's why I even thought it might have been the "Pause before TOD", but it wasn't.

Nothing worked in the aircraft, not only the MCDU, also the FCU the throttles the spoillers, overhead panel interaction... Nada!

I see…

In my recently experienced A343 crashes, it’s either a message, “Memory low, avionics will be disabled”, followed by dark (or flickering) cockpit screens, or the (now) widely-reported Orange WASM cockpit screens…

I’ve only had2 WASM freezes in the A340 since launch, and both were at the gate during setup, not during a flight. One of them was weird, because the systems froze, but there was no orange WASM crash screen. So I guess it was an actual freeze not a crash.

i fly the aircraft at least once a week. Several 10+ hour flights 

Edited January 26Jan 26 by Tuskin38

inibuilds products don’t work well for me either, and i have decided to pass on anything they put out. Carenado is the other. Bought their C182RG and they second i engage AP it nosedives. 

11 minutes ago, P_7878 said:

or the (now) widely-reported Orange WASM cockpit screens…

That’s a debugging feature Asobo added in SU4 which is why it’s only showing up recently 

Edited January 26Jan 26 by Tuskin38

1 minute ago, Tuskin38 said:

That’s a debugging feature Asobo added in SU4

That makes sense.

I have owned the A340/A350 since early release, but saw the Orange screens only recently for the first time. The explicit WASM indication on the screens clearly told me it was WASM error…

53 minutes ago, P_7878 said:

That makes sense.

I have owned the A340/A350 since early release, but saw the Orange screens only recently for the first time. The explicit WASM indication on the screens clearly told me it was WASM error…

I first few flights with the TDFI MD11, I got the frozen nonresponsive buttons and gauges. I've gotten the dead cockpit when loading the Just flight R45, F28, PMDG 737,777's. I deleted the WASM folder and uninstalled them. Rebooted computer and reinstall the product. Then reboot the compute again solved 98% of my issues.

4 hours ago, Bigmack said:

I deleted the WASM folder and uninstalled them. Rebooted computer and reinstall the product. Then reboot the compute again solved 98% of my issues.

Not really a great situation having to do that every time though.

The single only WASM issue I've ever had since MSFS 2024 launch, was 2 days ago on my first few attempted flights with the Ini A340.   Never had any issues with PMDG etc.  If you do some researching online, there are many more reports of these issues with the In A340 than with any other aircraft or dev.

I'm enjoying the A340 - able to use only the EIS2 model (the EIS1 models always freeze up for me) on short <2.5hr flights. 

But it's a serious situation and until it's fixed and stable, I'd never buy another Ini product at this point in time.

What I also find strange is that - in my dealings with Ini Support - the questions they ask and the suggestions they make are as though they've never heard of this issue 😄  It's really bizarre.   If you Google "Ini A340 freezes up" there are countless posts, on the Ini forums.  They ask you to record videos for them.   Great way to spend your time - setting up a flight in the A340 and flying it until everything freezes, so that they can see everything frozen in a video.  It honestly felt like they were just killing time with their support suggestions.   

Edited January 26Jan 26 by JYW

On 1/26/2026 at 10:08 AM, Bigmack said:

I first few flights with the TDFI MD11, I got the frozen nonresponsive buttons and gauges. I've gotten the dead cockpit when loading the Just flight R45, F28, PMDG 737,777's. I deleted the WASM folder and uninstalled them. Rebooted computer and reinstall the product. Then reboot the compute again solved 98% of my issues.

Bill:

I do not have direct access to a WASM folder (to delete) ...on my Xbox X...🙂...but I understand there are indirect (more involved) ways to achieve the same results.

Anyway, I just re-installed the A340 VIP v1.0.7 last week (after deleting the prior v1.0.6 from My Library). So far so good, no more issue with either Standard Pax A343 or VIP Edition A343...

Hopefully, I don't have to go through such above (inconvenient) steps, but I will keep in mind.

Thanks.

Edited January 27Jan 27 by P_7878