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