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
Load the A350 (cold & dark or ready state)
Program FMS 1 normally → works fine
Switch to FMS 2
Select “FMS 2”
→ The entire MCDU 2 freezes
→ No interaction possible
→ Loading a state shows the same issue
→ 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