Hi

After a recent reinstallation of MSFS2024, I've been progressively re-introducing my aircraft.  Most of them are working fine - streamed ones and 3rd party.  But I cannot get the Inibuilds A340 to work.  When I try to start the flight, I get all orange screens with the declaration that there has been a WASM failure.  I've tried the 'Disable' and re 'Enable' routine, and I've Downloaded the aircraft in MSFS2024 but it makes no difference.  Any thoughts of something I have or haven't done, or things I might try?

 

 

29 minutes ago, AJZip2 said:

Hi

After a recent reinstallation of MSFS2024, I've been progressively re-introducing my aircraft.  Most of them are working fine - streamed ones and 3rd party.  But I cannot get the Inibuilds A340 to work.  When I try to start the flight, I get all orange screens with the declaration that there has been a WASM failure.  I've tried the 'Disable' and re 'Enable' routine, and I've Downloaded the aircraft in MSFS2024 but it makes no difference.  Any thoughts of something I have or haven't done, or things I might try?

 

 

Did you try to delete the 340 WASM folder and then restart 2024 and let it recompile the 340 again?

See 

Don't own the 340 myself but that WASM folder could very well be

C:\Users\XXX\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\inibuilds-aircraft-a340

Edited January 9Jan 9 by DAD

There are WASM errors on practically all addon aircraft.

58 minutes ago, DAD said:

Did you try to delete the 340 WASM folder and then restart 2024 and let it recompile the 340 again?

See 

Don't own the 340 myself but that WASM folder could very well be

C:\Users\XXX\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\inibuilds-aircraft-a340

Thanks for the suggestion.

I deleted the WASM folder for the a340, and checked that it had gone, then uninstalled the downloaded version and disabled the streaming of it.  Then rebooted, re-enabled the streaming of it, went to boot it up and exactly the same issue (it booted up very quickly which surprised me if it was supposed to have been rebuilding the WASM).

I'll go through the whole routine again this evening just in case I missed a step.

 

Such WASM crash threads always bother me, because they are indeed real and widely reported on-line, for both PC and Xbox users (less so for Xbox, I think)…

I routinely fly the A340 and A350 on my MSFS2024/Xbox (thanks to iniBuilds) and have never encountered such crashes. 

I read (and believe) that they are not due to Xbox compatibility…🙂…

There does not seem to be a definitive solution either, but only trial and error methods. I also thought it was only the A350, but seemingly the A340 too…two such nice Airbus to fly in our SIM..

Hope, it gets resolved for the OP. 

5 minutes ago, P_7878 said:

Hope, it gets resolved for the OP.

And to the OP, my experience currently with the 340 is thus.  Spawn on RWY and RED screens are guaranteed.  Spawn cold n dark at gate, fire up APU or GPU and screens come on with no issues.  YMMV. TANSTAAFL. Blue skies,

-A

1 hour ago, btacon said:

Spawn on RWY and RED screens are guaranteed.  Spawn cold n dark at gate, fire up APU or GPU and screens come on with no issues

Oh this is probably why I’ve never seen it! I always start cold and dark at a gate. 

Sadly it's a work around and not a solution. For me, it is the worst kind of issue - things can be good for a while then it triggers. All of the usual WASM fixes don't work as it will manifest itself again.

3 hours ago, btacon said:

And to the OP, my experience currently with the 340 is thus.  Spawn on RWY and RED screens are guaranteed.  Spawn cold n dark at gate, fire up APU or GPU and screens come on with no issues.  YMMV. TANSTAAFL. Blue skies,

-A

I agree...the trouble is that spawning cold and dark was where I was starting off from.  But three frustrating days later (all sorts of issues I've never come across before) I then tried either 'Ready' state or at the runway, and that's when I get the orange screens.  But, basically, since I last flew this (SU3) I cannot get it in the air at all - and it was my go-to aircraft in MSFS2024SU3 and almost always from cold and dark.

But since I posted this it's got REALLY weirder - to the point that I will post a new thread once I've finished all of my checks and tests...it's ALL of my Airbus types that I am having problems with:

- The inibuilds A340

- The Fenix A320's (all of them)

- the Asosbo A320 Neo V2

 

I can't get ANY of them to fly - cold and dark or 'Ready' State.

As the A340 is a totally different beast and builder, I wondered if it was some weird quirk from my WingFlex 320 FCU unit (boots up with the 320's but not with the A340 but I don't know if it boots up partly by recognising the Airbus name in the logic) clashing with something done in SU4...but I've deleted that software and it made no difference.

And here's the crunch.  While the A340 hasn't been introduced in MSFS2020, the 320 Neo V2 is on both sims and the Fenix A320's also is...and they still work great in MSFS2020.  They run great whether started fom Cold and Dark or spawned at the runway.

Crazy stuff but at least I have a solution for my airliners: I shall fly Boeing 737's etc - and anything non Airbus in the name - in MSFS2024; I shall fly anything with Airbus in the name in MSFS2020 😆

I've spent the last week thinking I was going crackers...but it's not me, it's my sim!! 😇

Thanks for the input folks but clearly the problem I thought I had isn't the problem I actually have.  I'll start a new thread as soon as I can. 

Edited January 9Jan 9 by AJZip2

Something else is clearly going on with your SIM that goes beyond just the iniBuilds (Airbus) a/c specific WASM crashes…

And yes, it’s not you but your SIM…🙂…

Good luck…!

15 hours ago, P_7878 said:

Something else is clearly going on with your SIM that goes beyond just the iniBuilds (Airbus) a/c specific WASM crashes…

And yes, it’s not you but your SIM…🙂…

Good luck…!

Got it!!

I woke up and thought about it.  What does everything 'Airbus' use in common...my Controls settings!!  Because the airbuses have a different way of setting for reverse thrust in MSFS, I have a settings control for my Boeing flights and another for my Airbus flights.

And I then remembered what PMDG suggested to get my Boeing737-800 working post SU4.  They said 'Remove ALL of your control settings from ALL of your Hotas Items and start from scratch'.  Even though there were no spurious commands there, I did just that...and the PMDG then worked OK.

So this morning, I used the PMDG settings on my stock A320 Neo V2 ... and it worked!

So I then went to the Fenix A320, again with the new PMDG Boeing settings...and that now works too.

And in the meantime, I see from the thread about the impending release of the A340 update direct from Inibuilds that LOADS of folks have been having WASM crashes on the present A340 since SU4.

So my two conclusions are:

- SU4 has done some random and invisible messing with previously saved controls settings.  My further tests was that is was the yoke settings that have been messed up, even though the symptoms come through on the throttle response...which is bizarre.

- SU4 has caused some widespread havoc with the A340 WASM

 

SU4 is for me, otherwise, great - so I'll just get on and wipe ALL of my HOTAS settings and start again from a blank canvas with those...

...and wait for the updated A340 and buy direct from Inibuilds.

Once more, many thanks for your input 

Edited January 10Jan 10 by AJZip2

And just a final final...and back to where I started with the A340, I have FINALLY got a successful flight with the present A340 in SU4!

- Like many other folks here, I find that trying to start at the runway still produces immediate WASM crashes with orange screens

- But - using my sanitised PMDG737 yoke commands - I was at last able to boot up the A340 from Cold and Dark and actually achieve a flight all the way to touchdown and parking.

It really shouldn't be this difficult but, as I said earlier, everything else about the SU4 update I do like very much.   

5 hours ago, AJZip2 said:

It really shouldn't be this difficult but, as I said earlier, everything else about the SU4 update I do like very much. 

What a journey. Glad you figured it out in the end. Enjoy SU4!

Oh wow, never would've thought about control profiles... In 2020 and 2024 I was getting sporadic wasm crashes in the 310 and on the forums I constantly see that the 300, 340 and 350 suffer from the same problems - that made me refrain from touching anything inibuilds-related. I had a couple crashes in the 777 but never had one on the fenix... Really hope that Asobo tackles the root cause of it as soon as possible.