... is finally announced to be released tomorrow.

So can we expect MCE to work with the AS A330 as is (apparently except for the few additional functions that don't exist in the AS A320) or is some work needed to adapt MCE to the A330?

 

13 hours ago, RALF9636 said:

... is finally announced to be released tomorrow.

So can we expect MCE to work with the AS A330 as is (apparently except for the few additional functions that don't exist in the AS A320) or is some work needed to adapt MCE to the A330?

 

MCE V2.8.2.0 just uploaded should be able to recognize aircraft and for now treat it as A320 from Aerosoft with most switches and dials expected to be under FO's diligence, since it's more or less the same cockpit layout.

Except for Hydraulic panel, which will require some work, as FO should be able to handle those switches on request just as he does with others.

There could also be FMC-CDU changes (with regards ground services requests), but that's a formality.

 

Thanks for the quick update.

It works fine with the A330 overall and I am able to use all my voxscripts copied from the A320.

I did not thoroughly test everything but at first view the lights probably need some work (landing lights were not turned on) and also the APU seems not to be handled at all.

 

Thanks for feedback.

Hydraulic Panel will very likely need some work.

Should be dealt with next week.

On 12/12/2019 at 12:56 AM, FS++ said:

Thanks for feedback.

Hydraulic Panel will very likely need some work.

Should be dealt with next week.

You could also take a look at the flaps speeds.

1 hour ago, RALF9636 said:

You could also take a look at the flaps speeds.

You can try this.

Go to \Multi Crew Experience\Reference\ folder.

Copy "A320_ref.txt", paste it and rename it to something like "whatever_sim_name_in_aircraft_cfg_ref.txt"

whatever_sim_name_in_aircraft_cfg being "sim=whatever_sim_name_in_aircraft_cfg" in A330 aircraft.cfg" file.

Then open the new file and edit speed limits

[FLAPS_MAX_SPEEDS]
1=230
2=200 
3=185
4=177

The above are the default max speeds for each flaps selection.

 

2 hours ago, FS++ said:

You can try this.

Go to \Multi Crew Experience\Reference\ folder.

Copy "A320_ref.txt", paste it and rename it to something like "whatever_sim_name_in_aircraft_cfg_ref.txt"

whatever_sim_name_in_aircraft_cfg being "sim=whatever_sim_name_in_aircraft_cfg" in A330 aircraft.cfg" file.

Then open the new file and edit speed limits

[FLAPS_MAX_SPEEDS]
1=230
2=200 
3=185
4=177

The above are the default max speeds for each flaps selection.

 

Thanks, will do that.

There doesn't seem to be a minimum speed for the flaps. Nevertheless MCE sometimes objects "speed too low" when I want the FO to retract the flaps. Most of the time that is correct if I remember correctly. But with the Aerosoft A330 he does not want to retract the flaps from 1+F to 0 because of "speed too low" even when above 240 kts. That never happened in the A320 (FSL).

While we are at it. Though the FO sometimes correctly objects if I want to retract the flaps too early in the FSL A320 there is no such warning when the command is "Slats up" (instead of "flaps up"). That becomes a problem sometimes when MCE misunderstands my "flaps two" as "slats up/off etc.", which sometimes happens. MCE then retracts the flaps without a warning when I wanted to set flaps 2 which results in interesting approaches...

So could you please re-check the behaviour with speeds too low when retracting flaps and slats.

 

3 hours ago, RALF9636 said:

Thanks, will do that.

There doesn't seem to be a minimum speed for the flaps. Nevertheless MCE sometimes objects "speed too low" when I want the FO to retract the flaps. Most of the time that is correct if I remember correctly. But with the Aerosoft A330 he does not want to retract the flaps from 1+F to 0 because of "speed too low" even when above 240 kts. That never happened in the A320 (FSL).

While we are at it. Though the FO sometimes correctly objects if I want to retract the flaps too early in the FSL A320 there is no such warning when the command is "Slats up" (instead of "flaps up"). That becomes a problem sometimes when MCE misunderstands my "flaps two" as "slats up/off etc.", which sometimes happens. MCE then retracts the flaps without a warning when I wanted to set flaps 2 which results in interesting approaches...

So could you please re-check the behaviour with speeds too low when retracting flaps and slats.

 

OK, wilco

The speeds in ref files are the maximum speeds to be observed before extending to a specific flaps detent.

For retraction, he reads "F", "S" speed and "Green dot" speeds and makes decisions based on that.

Maybe a few things changed there as well.

He can't read those on FSL A320, therefore a different method is used.

What about CDU 2 ground services selection?

 

 

2 hours ago, FS++ said:

What about CDU 2 ground services selection?

 

 

Haven't tested that yet (I am used to the FSL doing these things on its own). But since there is a third MCDU for that stuff now, I guess it needs to be redone.

Just to update everyone.

It's works in progress since yesterday.

The bulk of the work will be on the very different Hydraulic panel, the additional fuel panel items as well as new (now functional Elec panel items)

Should have an update by the end of the week, with full integration to the MCE system.

Now fully supported in this package

You'll notice, 3 special testing flows are included.

They are there to help you get an idea about some the verbiage to use to manipulate any VC switch in A330.

Not all commands are included though.

 

Great, thanks. First flight looked good so far.

Apart from:

FO still does not want to retract flaps even above 230 kts due to speed too low.

 

And the next Bus is waiting... 😉

 

1 hour ago, RALF9636 said:

Great, thanks. First flight looked good so far.

Apart from:

FO still does not want to retract flaps even above 230 kts due to speed too low.

 

And the next Bus is waiting... 😉

 

Thanks for feedback.

In general, those warnings don't mean refusal to obey. Maybe voice intonation isn't there. Fo just wants confirmation when in doubt. Just say "go ahead", "do it", "execute", "don't argue", "positive", "without a doubt", "affirmative", "yes" etc... and he'll carry on the command. since you're the one calling the shots anyway.

Same with suggestions about max flaps, gear extension speed or other.

 

1 hour ago, FS++ said:

Thanks for feedback.

In general, those warnings don't mean refusal to obey. Maybe voice intonation isn't there. Fo just wants confirmation when in doubt. Just say "go ahead", "do it", "execute", "don't argue", "positive", "without a doubt", "affirmative", "yes" etc... and he'll carry on the command. since you're the one calling the shots anyway.

Same with suggestions about max flaps, gear extension speed or other.

 

I know, I do that.

But the FO shouldn't be worried about a too low speed in the first place (even above 230 kts). And he is not in the smaller busses (FSL), where I never had that problem. So there is something flawed regarding the A330.

15 hours ago, RALF9636 said:

I know, I do that.

But the FO shouldn't be worried about a too low speed in the first place (even above 230 kts). And he is not in the smaller busses (FSL), where I never had that problem. So there is something flawed regarding the A330.

He should worry about speed being too slow (obviously not above 200 knots).

Issue related to him not always getting "S" speed all the time as he used to with A320.

Download this replacement dll

Replace "mcasoftA3X.dll" in \Prepar3D v4\MCE dlls\

With new dll, whenever he can't read S speed, it defaults to 170 knots minimum. New dll already in latest official release.