iniBuilds A350 – FMC 2 Completely Frozen / Unusable – Aircraft Unflyable

[Thomas Kant]

Product: iniBuilds A350 Version: 1.1.7 / Nov 21, 2025
Simulator: MSFS 2024
Issue: FMC 2 freezes instantly and becomes completely unresponsive
Price Note: This is a €90 aircraft with multiple updates already released — yet this critical issue still exists.

---

Issue Description

Whenever the A350 is loaded — either cold & dark or using a ready state — the FMS 2 becomes completely unusable.

The freeze happens immediately after selecting:

• FMS 2 → “FMS 2”

From that moment on:

• All keys stop responding

• No LSK works

• No return/menu/INIT/PERF pages can be accessed

• The page cannot be exited

• The system stays permanently frozen

This makes the aircraft 100% unflyable, since a non-functional FMS 2 breaks normal A350 operation.

Even loading a saved state causes the exact same freeze, so the issue is fully reproducible every single time.

---

Screenshot Evidence

---

Steps to Reproduce

1. Load the A350 (cold & dark or ready state)

2. Program FMS 1 normally → works fine

3. Switch to FMS 2

4. Select “FMS 2”

5. → The entire MCDU 2 freezes

6. → No interaction possible

7. → Loading a state shows the same issue

8. → Aircraft becomes unflyable

This occurs every single time.

---

What Has Been Tried (Without Success)

• Restarted simulator

• Loaded different panel states

• Loaded saved states

• Restarted aircraft multiple times

• No mods installed

• No external hardware panels used

• Verified hardware inputs

• FMS 1 works normally

• Only FMS 2 is permanently frozen

---

Why This Is a Critical Problem (and price-relevant)

It is difficult to understand how a €90 aircraft, after numerous updates, can still have a core avionics bug that:

• breaks basic cockpit operation

• prevents proper flight planning

• blocks performance entry

• prevents flows and SOPs

• makes the aircraft entirely unusable for normal flying

A frozen FMS is not a minor issue — it’s a game-breaking flaw that completely stops the aircraft from being flown correctly.

This should not happen at this price point and at this stage of development.

---

Requested Resolution

• Investigation of the FMS 2 freeze

• Confirmation that the issue is acknowledged

• Hotfix or workaround

• Clarification whether this will be addressed in the next update

 

[Thomas Kant]

After deleting the WASM data - the FMC 1 and 2 work but now the aircraft no longer retracts its landing gear ... INI, what's going on here? 

[Thomas Kant]

After I removed all the paint jobs and also the Cabin Packages I and II from ini, I was able to take off from Dubai to Prague today. Let's see how it goes.

@INI, please provide detailed instructions on what to do after the update. 
Why are Cabin Packages I and II no longer compatible?
I would have expected a notification. Perhaps we will have to write the code ourselves in the future... Irony off...
For 90 euros, I expect something different...

[IniSteve]

Hi Thomas. Understand the frustration but this doesn't seem to be a widespread issue. Can you share your autosave and OFP/Flightplan details so we can try and reproduce the crash internally? 

Quote

Why are Cabin Packages I and II no longer compatible?
I would have expected a notification. Perhaps we will have to write the code ourselves in the future... Irony off...

The changes made to the model to reduce node and bone counts were really necessary, and not just for those on low-end hardware but even for those on higher end hardware, especially Intel and non-x3d chips. As mentioned in our post these changes significantly reduced stutters when looking around the aircraft or changing views, which of course benefits all of us even on the highest end chips and also helps with stability as these stutters can affect that as well.

Regarding the cabin packs, unfortunately these changes broke them completely, and they were already very difficult for us to maintain as any minor changes to the interior 3d models had to be repeated manually for every cabin pack across every variant. With this change, it was a bit of a final straw, and we've decided that the time and resources needed to maintain them is simply not sustainable for us as these efforts are better focused on the core aircraft as well as our other upcoming projects. Hope that helps clear up the factors that led to our decision and helps everyone understand it wasn't taken lightly.

(for others following along, I deleted the other posts that were not relevant to OP's issue so we can all focus on helping him)