Hi,

The co-pilot in the Majestic Q400 no longer handles communications.

If I ask him to set a radio frequency, the co-pilot acknowledges the request; after a short while, he says it’s done, but the frequency hasn’t actually changed.

I know that with the MJQ400, the MCE interacts via parts of the 2D cockpit. Regarding communications, during the procedure, no window of any sort is displayed.

Thank you and Regards,

Richard.

P3Dv5

MCE V3.1.4.8

Majestic Q400 Pro.

8 hours ago, DrumsArt said:

Hi,

The co-pilot in the Majestic Q400 no longer handles communications.

If I ask him to set a radio frequency, the co-pilot acknowledges the request; after a short while, he says it’s done, but the frequency hasn’t actually changed.

I know that with the MJQ400, the MCE interacts via parts of the 2D cockpit. Regarding communications, during the procedure, no window of any sort is displayed.

Thank you and Regards,

Richard.

P3Dv5

MCE V3.1.4.8

Majestic Q400 Pro.

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

Deleted (double post)

Edited May 26May 26 by DrumsArt
Double post.

3 hours ago, FS++ said:

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

-I do have the “mcmjq400.dll” file, version 1.0.5.2.

Just to clarify, everything else works perfectly fine (flows, checklists, and so on...).

-I know that at one point, the communications were handled perfectly.

Below is the aircraft I’m currently using. I’ve tried other variants, but the problem is the same.

[fltsim.18]

title=MJC8Q400_WIF

sim=MJC8Q4

model=

panel=

sound=

texture=WIF

kb_checklists=mjc8q400_check

kb_reference=mjc8q400_ref

atc_id_color=0xffffffffff

atc_id=LN-WDF

ui_manufacturer=Bombardier

ui_type=MJC-8 Q400

ui_variation=Wideroe

ui_createdby=Majestic Software

description=Majestic Software Dash-8 Q400 Wideroe

atc_heavy=0

atc_airline=Wideroe

atc_flight_number=

As always, thank you for your support.

Regards,

EDIT: forgot to mention that I'm having the same issue with the transponder (code, status: on or standby). The transponder and the frequencies are on the same panel.

Edited May 26May 26 by DrumsArt

17 hours ago, DrumsArt said:

-I do have the “mcmjq400.dll” file, version 1.0.5.2.

Just to clarify, everything else works perfectly fine (flows, checklists, and so on...).

-I know that at one point, the communications were handled perfectly.

Below is the aircraft I’m currently using. I’ve tried other variants, but the problem is the same.

[fltsim.18]

title=MJC8Q400_WIF

sim=MJC8Q4

model=

panel=

sound=

texture=WIF

kb_checklists=mjc8q400_check

kb_reference=mjc8q400_ref

atc_id_color=0xffffffffff

atc_id=LN-WDF

ui_manufacturer=Bombardier

ui_type=MJC-8 Q400

ui_variation=Wideroe

ui_createdby=Majestic Software

description=Majestic Software Dash-8 Q400 Wideroe

atc_heavy=0

atc_airline=Wideroe

atc_flight_number=

As always, thank you for your support.

Regards,

EDIT: forgot to mention that I'm having the same issue with the transponder (code, status: on or standby). The transponder and the frequencies are on the same panel.

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