On 10/24/2024 at 12:33 PM, Burge said:

FBW A380 will  be at the gate very soon,are the devs going  to have a crack at this super bad boy

Cheers Barry 

Of course.

Will the newly released AVRO RJ Professional series for MSFS also be tamed by your esteemed copilot? These old ladies have way too many switches/buttons and I just wanna fly man. 

On 11/11/2024 at 12:50 PM, Andreq73 said:

Will the newly released AVRO RJ Professional series for MSFS also be tamed by your esteemed copilot? These old ladies have way too many switches/buttons and I just wanna fly man. 

If it is Just Flight Avro, chances are it's similar to JF BAE 146 which is already supported in MSFS.

From previous experience interfacing Quality Wings BAE146 & AvroJet series, if I remember well it's mostly the autopilot that is different.

If you are a MCE user, please contact [email protected] and assuming it's Just Flight Avrojet, we may get you going with the switches, flaps and things like that until it is fully interfaced later on.

 

 

Hi @FS++ I was just about to get the PMDG 777f that just released. Will it work with MCE without an update, or will you need to do something to make it work with MCE? Thanks!

6 hours ago, severniae said:

Hi @FS++ I was just about to get the PMDG 777f that just released. Will it work with MCE without an update, or will you need to do something to make it work with MCE? Thanks!

The PMDG SDK is the same for all variants.

The installer didn't know exactly where the MSFS Freighter version would be installed to, so made speculation based on the 300 series as well as previous 200/300/and freighter for P3D.

One thing MCE needs to do is enable the PMDG SDK via some ini file to ensure

[SDK]

EnableDataBroadcast=1

It's something you can always do manually if you notice MCE doesn't connect to the plane.

Please confirm whether the installer did that automatically.

Apart from that, MCE will interact with Freighter the same way it does with the 300 which is already fully supported.

 

 

Edited December 9, 20241 yr by FS++

On 12/9/2024 at 7:53 PM, FS++ said:

The PMDG SDK is the same for all variants.

The installer didn't know exactly where the MSFS Freighter version would be installed to, so made speculation based on the 300 series as well as previous 200/300/and freighter for P3D.

One thing MCE needs to do is enable the PMDG SDK via some ini file to ensure

[SDK]

EnableDataBroadcast=1

It's something you can always do manually if you notice MCE doesn't connect to the plane.

Please confirm whether the installer did that automatically.

Apart from that, MCE will interact with Freighter the same way it does with the 300 which is already fully supported.

 

 

Great news, will be giving it a go this weekend!

Incidentally, did you see FSL have finally released their airbus. I used to use it with MCE back in P3d, hopefully an easy one to interface given it's hopefully the same thing in the back end?

Thinking of buying the new FSLABS a321 for msfs2020 , but of course cant fly any airliner without MCE, so will it be supported ? If yes any timeline?

many thanks anyways 🙏

Edited December 13, 20241 yr by ayousry

15 hours ago, ayousry said:

Thinking of buying the new FSLABS a321 for msfs2020 , but of course cant fly any airliner without MCE, so will it be supported ? If yes any timeline?

many thanks anyways 🙏

This one is going to take a while.

Won't be able to hazard an estimate until we have a copy of the plane to work on.

Schedule quite heavy right now, with iFly 737 MAX to finish, FlyBywire A380, and FS2024 new planes like Inibuild A330, Asobo 737MAX, and a couple of others which all need a crew, not to mention maintenance on planes that are already supported which keep updating all the time with the occasional need to re-work something and X-Plane which is due for an update that was delayed many times.

TFDi MD-11 was another one that was considered.

Too many planes showing up at the same time 🙂.

 

Understood , but at least can i have basic commands with it , flaps gears lights and thats it for now?

15 hours ago, ayousry said:

Understood , but at least can i have basic commands with it , flaps gears lights and thats it for now?

No worries regarding that.

From experience, even on non-supported planes, you can expect the gear, flaps and VHF tuning to be handled on any plane.

 

 

On 12/14/2024 at 2:37 PM, FS++ said:

No worries regarding that.

From experience, even on non-supported planes, you can expect the gear, flaps and VHF tuning to be handled on any plane.

 

Just tried it, unfortunately I get the 'please restart from the menu ' error and MCE closes so it doesn't appear to work in basic mode?

21 hours ago, severniae said:

Just tried it, unfortunately I get the 'please restart from the menu ' error and MCE closes so it doesn't appear to work in basic mode?

Do you mean PMDG 777 or FsLabs A320?

If it's the latter, please copy and paste the [fltsim.X] sections found in "aircraft.cfg".

Unlike with Prepar3D, each plane needs to be known to MCE even if it's not fully supported yet..

Edit: Probably detecting the plane as A320, and since it can workout it's not Fenix or Inibuilds A320 very likely assumes it's FlyBywire A320 and obviously can't detect the custom variables it is assumed to interact with as it's not FBW.

Edited December 18, 20241 yr by FS++

On 12/17/2024 at 11:00 PM, FS++ said:

Do you mean PMDG 777 or FsLabs A320?

If it's the latter, please copy and paste the [fltsim.X] sections found in "aircraft.cfg".

Unlike with Prepar3D, each plane needs to be known to MCE even if it's not fully supported yet..

Edit: Probably detecting the plane as A320, and since it can workout it's not Fenix or Inibuilds A320 very likely assumes it's FlyBywire A320 and obviously can't detect the custom variables it is assumed to interact with as it's not FBW.

Here is an example from one of the Aircraft.cfg files:

[FLTSIM.0]
title="FSLabs A321-231 - British Airways (G-EUXL)"
model=""
panel= "BAW G-EUXL"
sound=""
texture="BAW G-EUXL"
description=" Created by: FSLabs | Anthony Eyre"
wip_indicator=2
ui_manufacturer="Airbus"
ui_type="A321"
ui_variation="British Airways (G-EUXL)"
ui_typerole="Commercial Airliner"
ui_createdby="FSLabs"
ui_certified_ceiling=39000
ui_max_range=3500
ui_autonomy=7
ui_fuel_burn_rate=5300
atc_id="G-EUXL"
atc_airline="Speedbird"
atc_flight_number="321"
atc_heavy=0
atc_parking_types="GATE,RAMP,CARGO"
atc_parking_codes="BAW"
isUserSelectable=1
isAirTraffic=0
canBeUsedByAITraffic=0
sim=A321
kb_checklists=AirbusA321_check
kb_reference=AirbusA321_ref
atc_model=A321
atc_type=Airbus
sharklets=0
engine_variant=IAE2533A5
system_variant=EIS2
selcal_id=ACJL
version=1
airline_iata_code=BA
cruise_speed=477
icao_airline=BAW
ui_powerplant_specifics=IAEV2533-A5 Engine
ui_instrumentation=Wingtip Fences
ui_thumbnailfile=Texture.FSL\thumbnail.jpg

On 12/19/2024 at 12:33 PM, severniae said:

Here is an example from one of the Aircraft.cfg files:

[FLTSIM.0]
title="FSLabs A321-231 - British Airways (G-EUXL)"
model=""
panel= "BAW G-EUXL"
sound=""
texture="BAW G-EUXL"
description=" Created by: FSLabs | Anthony Eyre"
wip_indicator=2
ui_manufacturer="Airbus"
ui_type="A321"
ui_variation="British Airways (G-EUXL)"
ui_typerole="Commercial Airliner"
ui_createdby="FSLabs"
ui_certified_ceiling=39000
ui_max_range=3500
ui_autonomy=7
ui_fuel_burn_rate=5300
atc_id="G-EUXL"
atc_airline="Speedbird"
atc_flight_number="321"
atc_heavy=0
atc_parking_types="GATE,RAMP,CARGO"
atc_parking_codes="BAW"
isUserSelectable=1
isAirTraffic=0
canBeUsedByAITraffic=0
sim=A321
kb_checklists=AirbusA321_check
kb_reference=AirbusA321_ref
atc_model=A321
atc_type=Airbus
sharklets=0
engine_variant=IAE2533A5
system_variant=EIS2
selcal_id=ACJL
version=1
airline_iata_code=BA
cruise_speed=477
icao_airline=BAW
ui_powerplant_specifics=IAEV2533-A5 Engine
ui_instrumentation=Wingtip Fences
ui_thumbnailfile=Texture.FSL\thumbnail.jpg

Thanks.

Please re-download and install the full package (V3.1.1.0) using the link provided to you via e-mail or request it from [email protected]

The plane should now be identified but don't expect much to happen other than Gear lever handling, perhaps VHF tuning and if lucky flaps handling.

You need a fiull install because new files and folders need to be added to the main installation folder to cover iFly 737MAX, FlyBywire A380 and Inibuilds A330 which are now fully supported.

 

Hi,

 

Would be nice to have the Inibuild A350 supported. Thanks