Missing nose gear and cockpit displays not powering up.

[Eurosky]

Gents, bit of a strange one. On latest Beta FS2024. I uninstalled and reinstalled the aircraft, deleted WASM etc. Upon loading the aircraft, nose gear/strut is missing. Nose gear door showing open. Cockpit displays are not starting up, all black. Engines are running but not spinning/rotating in external view.  Tiller/rudder moves the aircraft, but no visual rudder/tiller movement in the cockpit. 

Side note, I see user "Der Michel" is taking his time and doing a phenomenal job picking up and giving valuable feedback to the development team and to the community. Much appreciated Sir. Phenomenal job and thank you. 

Christian

A380 driver.

Edited June 21 by Eurosky

[foliainfx]

38 minutes ago, Eurosky said:

Gents, bit of a strange one. On latest Beta FS2024. I uninstalled and reinstalled the aircraft, deleted WASM etc. Upon loading the aircraft, nose gear is missing, and the cockpit displays are not starting up. Green gpu lights are available but does nothing when actioned. 

Any suggestions appreciated.

Christian

Does it work with the normal 2024 version? Try clearing your wasm folder.

Edited June 21 by foliainfx

[Soupta]

Yeah just to add that I've got the same thing here. Done all the usual reinstalls and wasm clears. Seeing a few posts on the MSFS forums about it so I guess it's just a broken patch by asobo.

[pablitooaguilaar]

I have the very same issue but with the normal version od MSFS24. I already tried deleting the WASM, doing a full reinstall but nothing works.

[draytonk]

Yes me too, see post below this 

[Ben757]

I'm having same issues, I've done a fresh install of absolutely everything and it's still the same

[Ben757]

I just fixed mine, I was opted into the open beta, I opted out and msfs2024 updated on opening and it's working fine now.  

[pablitooaguilaar]

How did you do it???? To exit the beta I mean

 

[Xenon341]

Message from the ini discord : 

 

Quote

Rich [UTC+8] — 17:11

@here Thanks for your reports. What has happened is that the WASM has failed to initialize. As such anything that relies on WASM to operate will not work as expected. It is normally a rare situation that can happen at any time, in either sim on any version of it thereof. Similar behaviours can be seen after a WASM crash when dependent items become unresponsive. However, this is a guaranteed occurence on latest SU3 Beta affecting all WASM modules compiled with SU2 SDKs. It is not limited to the A350 or iniBuilds for that matter. It needs a "fix" or reversion sim-side to resolve. If you're an affected user, we recommend reverting to SU2 meanwhile as this is not an issue there. We do not guarantee compatibility with SU Betas generally. Thanks.