iniBuilds A350 Airliner V1.2.4 Update 🚀

v1.2.4 for the iniBuilds A350 Airliner is now available. This update resolves several key flight logic and navigation issues, including incorrect descent mode behaviour, overlapping step climbs on the position report page, and inaccurate fuel burn predictions. Fixes have also been made to premature auto-rotation, incorrect DME/VOR display, and unrealistic ADS-B vertical speed readings, alongside refined roll sensitivity for improved handling.

An EFB update also introduces an in-flight maintenance override, allowing users to repair items during flight.

This update can be downloaded via the iniManager.

____________________________________________________________
V1.2.4
SYSTEMS ⚙️
FIXED Aircraft had inadvertently entered descent mode and it was impossible to re-enter climb mode
FIXED Having multiple planned step climbs causes them all to overlap on the position report page
FIXED Fuel burn predictions in MCDU are inaccurate
FIXED Aircraft auto rotating prior to v1
FIXED DMEs display as VORs
FIXED ADS-B readout shows unrealistically high vertical speeds
FIXED Adjusted roll axis sensitivity based on user feedback.

EFB📱
ADDED Override for maintenance items to be repaired in-flight

Edited March 18Mar 18 by MrLamb

Thanks, @MrLamb.

I plan to bypass the v1.2.3 and test this v1.2.4 instead, when I can.

Cheers…!

Well that didn't take long. Might as well call this a hotfix.

I just had my first WASM crash in over 8 months with the A350. Five steps backwards, again.

36 minutes ago, marlon445 said:

I just had my first WASM crash in over 8 months with the A350. Five steps backwards, again.

Don’t just update it.  Delete it, remove left overs from community and all MSFS folders and fresh install.

4 hours ago, marlon445 said:

I just had my first WASM crash in over 8 months with the A350.

Same here.

4 hours ago, Dreamflight767 said:

Don’t just update it.  Delete it, remove left overs from community and all MSFS folders and fresh install.

That; what I do. I never update. just uninstall and reinstall and a reboot. No wasm incidents so far.

Autorotating? wow. 

11 hours ago, Bigmack said:

That; what I do. I never update. just uninstall and reinstall and a reboot. No wasm incidents so far.

Yes. Myself being on Xbox/Marketplace, I recall that I never actually see an option to update this product in My Library (from the previous version), as is customary for other products.

So, basically, I always (have to) re-install the latest version (directly) from the Marketplace every time.

Maybe that’s the reason, I’ve encountered WASM errors, rarely ever…not sure…

Cheers…!

11 hours ago, Tuskin38 said:

Same here.

@Tuskin38

I do recall, you have been one of those fortunate A350 users on the PC, immune to WASM (those orange-colored flight deck screens still give me a bit of nightmare…🙂…)…

Hope, a fresh install and clearing of the community folder etc. gets you back in the pilot’s seat of this one..

Why are WASM crashes so common in flight simulator now?

Just now, simsuper80 said:

Why are WASM crashes so common in flight simulator now?

One possible reason could be that WebAssembly is ideally suited to hiding DRM measures – that is, 'tunneling' the relevant code. I'd bet there's a lot of experimentation going on in this area.

Yes, clearly, something new (experimental?) has been going on since late 2025 and in early 2026, in MSFS.

That’s why the WASM reports have lately proliferated, especially for some airliners, that were (mostly) immune to it before.

Also, I understand that the (now well-known) “Orange” WASM screen notification was introduced as an added diagnostic tool, in SU4. So, the WASM was present earlier too…

A350 2020 users were also getting WASM crashes.

Just finished OMAA-YSSY in real time, no issues.

Edited March 20Mar 20 by Tuskin38