iniBuilds A320/21/30 compability with Winwing MCDU

[JDiercks]

Hello!

is there any update on compability with the Winwing MCDU and iniBuilds included Airbusses in MSFS2024

jesper

[A340iB-2025]

Yes please, especially the A330 would be nice to have it working with the MCDU.

[Arty57]

I believe this will not get addressed in the short or even medium term.  Simply put ini’s design decision to group multiple instruments into one popup instead of single popup’s for single instruments.  This means that WinCTRL has only one data stream for six or so instruments. Lots of opportunities for collisions and connections to be lost.  Single popups mean singular data channels.  No Collisions, much less chance of connectivity failures.  This is my understanding of the situation based upon months of working to get a resolution for the WinCTRL MCDU screen freezing when used with the iniBuilds a340-300.  Identical hardware MCDU, FCU and EFIS and the WinCTRL software, SimApp Pro (any recent version).  The Fenix and FSLabs planes both use one popup for one instrument. Both Fenix and FSLabs airbuses perform flawlessly 99% of the time. IniBuilds not so much.  The a340-300 is the only ini plane that can talk to external MCDU (FMC/keyboard), unfortunately it keeps losing it’s voice. When that occurs the screen locks up.  Notably the keyboard and LSK’s still function and can be witnessed on MCDU in virtual cockpit but the screen locks up.  Unplugging and reconnecting fixes it or switching off/on with a switched hub OR changing focus of MCDU from Pilot to co-Pilot in the SimApp Pro software all fix the freeze, until the next one.  Very random, sometimes 10 minutes into flight, sometimes 30 but always it will freeze. No matter what your perspective there is no denying it totally kills the immersion of the external hardware.

The fact that WinCTRL and/or iniBuilds remain completely silent on this well known bug is telling. Make of it what you will

-A

[JDiercks]

On 3/1/2026 at 3:13 AM, Arty57 said:

I believe this will not get addressed in the short or even medium term.  Simply put ini’s design decision to group multiple instruments into one popup instead of single popup’s for single instruments.  This means that WinCTRL has only one data stream for six or so instruments. Lots of opportunities for collisions and connections to be lost.  Single popups mean singular data channels.  No Collisions, much less chance of connectivity failures.  This is my understanding of the situation based upon months of working to get a resolution for the WinCTRL MCDU screen freezing when used with the iniBuilds a340-300.  Identical hardware MCDU, FCU and EFIS and the WinCTRL software, SimApp Pro (any recent version).  The Fenix and FSLabs planes both use one popup for one instrument. Both Fenix and FSLabs airbuses perform flawlessly 99% of the time. IniBuilds not so much.  The a340-300 is the only ini plane that can talk to external MCDU (FMC/keyboard), unfortunately it keeps losing it’s voice. When that occurs the screen locks up.  Notably the keyboard and LSK’s still function and can be witnessed on MCDU in virtual cockpit but the screen locks up.  Unplugging and reconnecting fixes it or switching off/on with a switched hub OR changing focus of MCDU from Pilot to co-Pilot in the SimApp Pro software all fix the freeze, until the next one.  Very random, sometimes 10 minutes into flight, sometimes 30 but always it will freeze. No matter what your perspective there is no denying it totally kills the immersion of the external hardware.

The fact that WinCTRL and/or iniBuilds remain completely silent on this well known bug is telling. Make of it what you will

-A

Logical explaination, but really sad.

[iniSteven]

On 2/28/2026 at 9:13 PM, Arty57 said:

I believe this will not get addressed in the short or even medium term.  ...

Hi, this is incorrect.

1: The winwing MCDU *is* compatible with the A340, which is the only aircraft that uses these grouped instruments. Given the feedback we have received we do not plan to continue using this method for future releases. That said, the graphical display of the instruments has nothing to do with compatibility with Winwing peripherals. Regarding the disconnection issue, we are in contact with Winwing to solve this as many of us on the testing team use these peripherals and want them to work.

2: The A320, A321, and A330 are Microsoft products built by us under contract. As such, the scope and featureset of these aircrafts is determined by Microsoft.

[JDiercks]

21 hours ago, iniSteven said:

Hi, this is incorrect.

1: The winwing MCDU *is* compatible with the A340, which is the only aircraft that uses these grouped instruments. Given the feedback we have received we do not plan to continue using this method for future releases. That said, the graphical display of the instruments has nothing to do with compatibility with Winwing peripherals. Regarding the disconnection issue, we are in contact with Winwing to solve this as many of us on the testing team use these peripherals and want them to work.

2: The A320, A321, and A330 are Microsoft products built by us under contract. As such, the scope and featureset of these aircrafts is determined by Microsoft.

Thanks for the answer. Does #2 mean compatibility is not planned for these aircraft on short term?

[iniSteven]

10 minutes ago, JDiercks said:

Thanks for the answer. Does #2 mean compatibility is not planned for these aircraft on short term?

It means that it's not something we even can plan because it's not a decision we can make.

[Arty57]

On 3/5/2026 at 7:52 PM, iniSteven said:

Hi, this is incorrect.

1: The winwing MCDU *is* compatible with the A340, which is the only aircraft that uses these grouped instruments. Given the feedback we have received we do not plan to continue using this method for future releases. That said, the graphical display of the instruments has nothing to do with compatibility with Winwing peripherals. Regarding the disconnection issue, we are in contact with Winwing to solve this as many of us on the testing team use these peripherals and want them to work.

2: The A320, A321, and A330 are Microsoft products built by us under contract. As such, the scope and featureset of these aircrafts is determined by Microsoft.

Thank you Steven for an opportunity to retract my incorrect theory of root cause.  I have been more fully informed now and feel far more hopeful for a quick resolution.  Blue skies,

-A