What additional functionality do you exactly achieve by MCE reaching 2D MCDU panels? 

I really liked how MCE worked with FSL A320 with my MCE settings before in the past versions. I used Real cockpit Crew Coordination and Call-outs and monitoring functions, plus my custom commands in the VoxKey. There was no any interaction by MCE with MCDU 2D panels, but I never cared less about  procedure scripts offered by MCE so I wouldn't know any different even if MCE reached them in certain situations. 

I can understand there's some necessary functionality that you can only reach via manipulating 2D MCDUs and I can live with MCE juggling them at the start up once, no problem. But as I can see it is also tied up for example with GSX' PAX boarding and probably something else.  

I tried to modify [RAMP] section in mce.ini as follows:

[RAMP]
NoRampToOfficeTalk=1
NoPaxDoorsAutohandling=1
NoCargdoorsAutoHandling=1

However soon as GSX finishes boarding MCE pops up right MCDU and starts closing the Doors on its own again no matter of the settings above. Probably there are other situations where MCE also tinkers with these 2D panels that I wish I could avoid completely.

I renamed "mcfslA3X.dll" but I'm afraid that I also lost some of the FMA calls (that I like so much with MCE) and maybe some other useful functionality that I could use with voice commands. 

Could you make those [RAMP] switches above work with FSL A320X? At least that would eliminate the nuisance of having 2D MCDU panel pop up suddenly when I'm tinkering with 3D MCDU data?

What else does renaming of "mcfslA3X.dll" affect?

Many thanks. 

PS: MCE v2.7.5.4 here

Another hiccup (MCE v2.7.5.9) with FSL A320X, mcfslA3X.dll is disengaged:

When MCE starts it seems to send keystroke CTR+SHF+T, because it always shuts down UTLive AI traffic. So I have to press CTR+SHF+T to toggle UTLive back on. Could you fix this?

Thanks.

12 hours ago, Dirk98 said:

What additional functionality do you exactly achieve by MCE reaching 2D MCDU panels? 

I really liked how MCE worked with FSL A320 with my MCE settings before in the past versions. I used Real cockpit Crew Coordination and Call-outs and monitoring functions, plus my custom commands in the VoxKey. There was no any interaction by MCE with MCDU 2D panels, but I never cared less about  procedure scripts offered by MCE so I wouldn't know any different even if MCE reached them in certain situations. 

I can understand there's some necessary functionality that you can only reach via manipulating 2D MCDUs and I can live with MCE juggling them at the start up once, no problem. But as I can see it is also tied up for example with GSX' PAX boarding and probably something else.  

I tried to modify [RAMP] section in mce.ini as follows:

[RAMP]
NoRampToOfficeTalk=1
NoPaxDoorsAutohandling=1
NoCargdoorsAutoHandling=1

However soon as GSX finishes boarding MCE pops up right MCDU and starts closing the Doors on its own again no matter of the settings above. Probably there are other situations where MCE also tinkers with these 2D panels that I wish I could avoid completely.

I renamed "mcfslA3X.dll" but I'm afraid that I also lost some of the FMA calls (that I like so much with MCE) and maybe some other useful functionality that I could use with voice commands. 

Could you make those [RAMP] switches above work with FSL A320X? At least that would eliminate the nuisance of having 2D MCDU panel pop up suddenly when I'm tinkering with 3D MCDU data?

What else does renaming of "mcfslA3X.dll" affect?

Many thanks. 

PS: MCE v2.7.5.4 here

We only use CDU for the following.

Automatic handling of cargo and cabin doors when GSX or AES request it

Connection and disconnection of ground power

Setting and releasing chocks.

CDU 2 is used to refuel aircraft as well as set NAV1 & NAV 2 freq and radial on request.

Will check why disabling doors handling isn't working on your side.

Regarding "mcfslA3X.dll".

That's our tailored interface for that specific aircraft.

When MCE detects aircraft as the FSL A320 we support, it instructs fsInsider64.dll to load that specific dll through which MCE can read switches status and set them as required.

If the file with expected name is missing, fsInsider64.dll will default to loading "mcgeneric.dll" which as its name implies handles default aircraft or any unsupported aircraft that is coded to use P3D/FSX default variables. Many aircraft from Carenado or A2A fall into that category.

Obviously FSL A320 needs custom interfacing.

Each dlli  in <MCE dlls> folder is tailored for a specific complex aircraft. And only one of them is loaded at any given time. They could all have made it as separate "products", specifically designed for aircraft A1 or A2. We just can't bring ourselves to make a product for 3 to 4 months it takes to interface a complex aircraft. It's nothing compared to the 11+ years sunk into this product.so far. And we have the tech to handle pretty much any aircraft, with or without SDK.

With SDK, it could take as little as a month or two to interface one.

 

7 hours ago, Dirk98 said:

Another hiccup (MCE v2.7.5.9) with FSL A320X, mcfslA3X.dll is disengaged:

When MCE starts it seems to send keystroke CTR+SHF+T, because it always shuts down UTLive AI traffic. So I have to press CTR+SHF+T to toggle UTLive back on. Could you fix this?

Thanks.

By design, and this isn't tailored to a specific aircraft, unless you have indicated that you are using AES for ground services, MCE will look up the key combination that triggers GSX and fire it so that GSX Window pops-up and confirms user has GSX installed and running.

Default key is normally CTRL+SHIFT+F12

Either set the GSX trigger to something not related to UTLive, or go to MCE user interface, click <More options> button, then select "Use AES" so that MCE refrains from auto-popping GSX.window. 

It should also ignore all those messages in green bar coming from GSX, thus not attempting to handle doors on request as it normally does.

Many thanks for taking the time to explain all this, I'll go through and experiment with my settings.

Meanwhile:

1 hour ago, FS++ said:

By design, and this isn't tailored to a specific aircraft, unless you have indicated that you are using AES for ground services, MCE will look up the key combination that triggers GSX and fire it so that GSX Window pops-up and confirms user has GSX installed and running.

Default key is normally CTRL+SHIFT+F12

Either set the GSX trigger to something not related to UTLive, or go to MCE user interface, click <More options> button, then select "Use AES" so that MCE refrains from auto-popping GSX.window. 

It should also ignore all those messages in green bar coming from GSX, thus not attempting to handle doors on request as it normally does.

My GSX key is set to CTRL+F12, changing it to something else did not stop MCE killing UTLive on its start up (right before MCE's window pops up). Eventually I had to change Toggle Aircraft key binding in UTLive from CTRL+SHF+T to something like CTRL+SHF+S. That immediately stopped MCE interfering with UTLive - you may want to look into MCE code for this, otherwise I might need to go through MCE settings and cfg files.

Please advise.

Thanks

 

Edited April 26, 20188 yr by Dirk98

1 hour ago, FS++ said:

We only use CDU for the following.

Automatic handling of cargo and cabin doors when GSX or AES request it

Connection and disconnection of ground power

Setting and releasing chocks.

 

Regarding "mcfslA3X.dll".

Could you make the above optional in mce.ini please?

I really wouldn't like to rename "mcfslA3X.dll" and lose your tailored interface for FSL A320X completely.

Thanks!!

Edited April 26, 20188 yr by Dirk98

23 minutes ago, Dirk98 said:

Could you make the above optional in mce.ini please?

I really wouldn't like to rename "mcfslA3X.dll" and lose your tailored interface for FSL A320X completely.

Thanks!!

OK, will do.

 

I've noticed another problem with current MCE full v2.7.5.9 and FSL A320X, "mcfslA3X.dll" is ON:

I load FSL A320X in Turn around state, ADIRS are aligned. FD buttons are reset and On. Then I launch MCE.

Soon as MCE starts playing with MCDU 2D panels at launch Flight Director switches to TO mode, I mean the FD guidance lines appear on the PFD and the horizontal line shows TO pitch. I have to reset FD buttons so the FD guidance lines on PFD go away, but again when the MCE's GSX auto- door manipulation kicks in and 2D MCDU pops up the same happens.

This is basically why I'm so reluctant to use any of MCE's flows or auto functions.

Please fix it or better give editing means to turn certain functionalities On/Off.

Thanks, 

 

Edited April 26, 20188 yr by Dirk98

Another problem: 

Unfortunately when in idle MCE also sends some internal inputs to FSL A320X on its own regularly that affect FCU mode. It's easy to check: Start A320X, turn it on, allign IRS, reset FD ON/off/ON, start MCE. First you'll see at launch, right after accessing MCDUs, it will change FCU mode (look at PFD). Now you can reset FD On/off/On again and wait for 1-2 minutes. You'll observe the same behavior again, as if MCE fumbles with the rotaries, particularly often with HDG rotary to some reason.

 

The above never happens when "mcfslA3X.dll" is Off, so the culprit is obvious, but unfortunately I can't manage FCU with voice commands anymore.

Thanks,

2 hours ago, Dirk98 said:

Another problem: 

Unfortunately when in idle MCE also sends some internal inputs to FSL A320X on its own regularly that affect FCU mode. It's easy to check: Start A320X, turn it on, allign IRS, reset FD ON/off/ON, start MCE. First you'll see at launch, right after accessing MCDUs, it will change FCU mode (look at PFD). Now you can reset FD On/off/On again and wait for 1-2 minutes. You'll observe the same behavior again, as if MCE fumbles with the rotaries, particularly often with HDG rotary to some reason.

 

Getting the FCU displayed HDG, ALT, QNH and VS with this aircraft was a real challenge, as their location in memory changes every time you run the sim.

They aren't just offsets like you find on many other aircraft.

The dll has to literally scan the VAS in order to find them.

FO rotates the HDG and VS in order to make sure they aren't at zero. Otherwise he'll never find them.

Add to that the HDG in this aircraft is so realistic it doesn't even exist until about 10 minutes after you set IRUs to NAV.

This means starting from cold and dark, he won't find them all until about 12 to 13 minutes (search held back by HDG). Eventually, if no luck with FCU, once you have started engines, restart MCE and it should find them within 3 minutes (except SPD).

The key thing is not to reset HDG or VS to zero as the search goes on.

Obviously, if and when there is an SDK, it would be much easier. But for now, it's usable as it is.

Still no luck with SPD. Somehow, FO can only read value once airborne.

He'll start another search for SPD when passing 5000 above ground. This one shouldn't last more than a minute as he's only looking for 1 item.

When you ask FO to dial something in FCU and he says he's doing it while nothing is happening, just assume he didn't find the reference value to rotate the dial against. we deliberately prevent him rotating to meaningless values,

 

 

Thanks, Gerald.

I think I've found how to manage all this:

1. Don't load PAX with GSX - that will save you sudden MCDU conjuring after GSX reports PAX are loaded.  - This could be made an option in mce.ini, whereas MCE wouldn't manage doors and PAX loading in general.

2. Don't turn on FDs until right before you push off.

To some reason after GSX starts push back and you start engines MCE doesn't meddle with fcu anymore. And you can still enjoy FMA calls on take off and voice control of Altitude changes.

This is great taking the total lack of FSL SDK. 

Just please see if you can disable those functions that require 2D MCDUs in mce.ini

Cheers,

Edited April 26, 20188 yr by Dirk98

On 4/26/2018 at 8:48 PM, Dirk98 said:

Thanks, Gerald.

I think I've found how to manage all this:

1. Don't load PAX with GSX - that will save you sudden MCDU conjuring after GSX reports PAX are loaded.  - This could be made an option in mce.ini, whereas MCE wouldn't manage doors and PAX loading in general.

2. Don't turn on FDs until right before you push off.

To some reason after GSX starts push back and you start engines MCE doesn't meddle with fcu anymore. And you can still enjoy FMA calls on take off and voice control of Altitude changes.

This is great taking the total lack of FSL SDK. 

Just please see if you can disable those functions that require 2D MCDUs in mce.ini

Cheers,

Would you like the option to exclude ANY interaction with CDU, including Ground power connect./disconnect as well as chocks or just the doors handling part?

 

On 5/1/2018 at 1:23 PM, FS++ said:

Would you like the option to exclude ANY interaction with CDU, including Ground power connect./disconnect as well as chocks or just the doors handling part?

 

Oh sure, I would love this option to disable ANY interaction with CDU, including everything that requires invoking of 2D CDU panels.

Many thanks!

On ‎5‎/‎2‎/‎2018 at 3:22 PM, Dirk98 said:

Oh sure, I would love this option to disable ANY interaction with CDU, including everything that requires invoking of 2D CDU panels.

Many thanks!

OK, download this file, unzip and replace 2 dlls in \Prepar3D v4\MCE dlls\ folder

The "mcfslA3X.dll" has a config file named "mcfslA3X.ini"

Open it and add these 2 lines

[OPTIONS]

NoCduAction=1

It should prevent Fo handling any FMC-CDU