Source : on winwing’s page about the MCDU, in the description, search for “MCDU Platform Compatibility Schedule”, there’s a button “click to view details”, and this table appears.
I don’t know how much this info is up-to-date, though.
EFIS / FCU
I do own an FCU + EFIS config. What I can tell you, is that today, I can use both of them with the A320 by Inibuilds, with the software by WinWing. I also use it with general aviation,this time by using Mobiflight and a profile made by the community that I modified a bit (because the EFIS is not configured in this profile).
Hope for the next part
As you can see, the MCDU is not compatible, today, with the IniBuilds A320. It’s not totally on WinWing’s end, because they need IniBuild to let them connect to the MCDU; but they stated on their table that it is “upcoming”, and though I try not to be naive about company’s comitments, it’s a good light to me that Winwing said “we’re going to do this, as much as we can”;
As you can see here, there’s a lot of “MCDU Profiles for Mobiflight” that are created by our wonderful comunity.
This is why I have hope that everything will go right in the future, but maybe not “tomorrow”. Moreover, the A350’s computer is quite different than what we have in a A320, so I do think that there will be choices made by the artists on “how to make it feel good”.
I’m confident, but there are no certainty. I’ve thrown here the element so you can get your very own opinion and make the choice of buying or not, without me tampering you. Happy to answer more if you have any question
My experience with the MCDU is that currently, uin MSFS2024 it doesn’t work with iniBuilds’ Airbuses (not even with the A320 neo), but if they plan to implement compatibility with the A350 it will probably enable all the family. In MSFS2020 it shows the MCDU display, but I had to do a Mobiflight profile myself to have the buttons working.
Partially, but you need to install Mobiflight for now and then use the profile for the A400M Atlas which is also an iniBuilds aircraft. The EFIS (right or left) does nothing at the moment, but as a stop gap solution it’s better than nothing.
Let me explane the issue with iniBuilds Airbuses and the WinWing MCDU. I can tell you as a MobiFlight team member which issue we are facing with iniBuilds Airbuses and I think (I´m sure) WinWing have the same issue.
On the FSWeekend in Leylistad we showcased the latest MobiFlight Beta version and how it works with WinWing MCDU. All who visited us at the Mobiflight exhibition stand saw the FMS screen from MD-11 was streamed on the WinWing MCDU display. Also the green color of the letters and numbers was shown on the MCDU in green.
In the MobiFlight Beta Version we implemented an API, which pulls data from the Airplane. The API can only pull the data, if the Airplane have also an API implemented. Fenix have an API, FlybyWire have an API and the MD-11 you saw at FSWeekend have an API. But iniBuilds Airbuses don´t have an API and this is the problem. We can´t pull the needed data from the Airplane. iniBuilds needs to implement an API in their airplanes, otherwise we are not able to push the airplane MCDU data to the WinWing MCDU device. The MCDU buttons works fine with MobiFlight, also the FCU and EFIS works fine, but not the MCDU. We need to wait until iniBuilds implement an API in their Airbuses.