FS++

There is a separate Voxkey profile for each simulator. For MSFS 2024 & 2020, you need to open "FS2020.vkp" (might be called "FS2020 Demo.vkp") profile and add custom commands to that one. When MCE loads, it looks up the relevant profile for the currently running flight sim.

It will be a while for this one as the plate is full. If you own the plane, start a thread on their forum. If there is enough interest for a crew, it may take priority.

New package (V3.1.56) is now available for download. Adds support for Inibuilds A340 and fully tested with iFly 737 MAX SP1

Just received a message from iFly regarding release of SP1 for the 737MAX which is already supported. We'd rather not have to release 2 updates in the space of a week. Therefore, a few daya will be needed to check MCE integration with the MAX is as good as before, then a full package update will follow by mid-next week and will also support Inibuilds A340

It's been works in progress for a while now. We should have the first package that fully supports it by the end of next week. To same level as support for all Inibuilds A310/A300-600, A320, A330 & A350

The file has just been updated to catchup with changes made by Asobo in MSFS 2024 latet update. Confirm ATC feature still strong. Redownload using same link.

Ah, I remember now. VHF, NAV, ADF and transponser dialling is done differently than with other planes that have fully dedicated devices (737 example). FO, would typically pop-up his FMC CDU 2D panel, go to radios page and dial there using the pad. This means... 1 - You have to install with option 2D panels included. 2 - Let's hope Majestic didn't change the events that trigger the opening and closing of those panels. I mean those event that are sent when you press, SHIFT 1, SHIFT 2, SHIFt, 3...etc. one of them triggers the right side FMC CDU pop-op

From experience, all planes, even the most complex like PMDG 777, PMDG 747 use the default cariables for VHF radios. So FO is expected to always be able to do that even on non supported planes. Having said that, I don't own a copy of Majestic for P3D V5. Interfacing was done a very long time ago up to V4. Unless they pushed things further to the point where even radios dialling is custom, then cannot explain it. Assuming the plane in V5 isn't a radical departure from the previous one, go to \Prepar3D v5\ installation folder, open <MCE dlls> and check you have a "mcmjq400.dll". That is the dll that handles that plane. That dll doesn't load on its own. Only gets into P3D process when the plane is positivekly identified as the Q400 from mMajestic. I suggest you post [fltsim.X] sections found in aircraft.cfg so I can at least check the plane can be recognized and not treated as unsupported default plane. Go to

First, welcome aboard. It's not a regitration issue. More like a case of not indentifying the plane properly. Is it -200, -100 or Freighter. Is it a new variantthat was added recently. Are you using a third party livery (these sometimes cause issues). For now, use the default livery. Send "aircraft.cfg" file for the plane. Go to C:\users\your_user_name\AppDtata\Roaming\Multi Crew Experience\ and send Simco64_ldr.log as well [email protected] Thank you

Way out of date. Latest version that supports MSFS 2024, 2020, Prepar3D and FSX is V3.1.4.8 Anyone can request Demo download link from [email protected]

Not aware of the differences in CDU. Can only happen if CDU buttons control in SDK have different IDs in new variant. I suggest you contact support and send "aircraft.cfg". Thanks

There is an updated file. Same download link. Should restore ATC integration with SU5

Native ATC feaure broken in recent MSFS SU5, but will be sorted in te coing days

You need to un-install previous version, then download and install latest Multi Crew For X-Plane V1.8.0.2.

Happening on Windows 11 wih FSX Steam as well, and yes after some Windows update.