On 8/16/2024 at 2:23 PM, FS++ said:

I did notice when boarding, GSX stating "waiting for your action open open aft cargo door, open fwd cargo door" and MCE not taking any action because of the "NoCargoDoorsAutoHandling=1 ".

I tried with this option set to 0 and found that MCE opened the Overwing Emergency Exit instead of the FWD Cargo door and the R1 exit instead of the AFT Cargo door.

So this is the first part of the issue.

 

Quote

Is there a setting that actually gets GSX (or in Fenix options) to handle all doors automatically which I may not have enabled.

AFAIK Fenix automatically handles the doors when you load the aircraft via the "GSX" option in the EFB of the Fenix. Nevertheless I do see the issue also when I use the "Instant" option in the EFB and handle GSX via the GSX menu and the Fenix doors manually via the EFB. So that doesn't make a difference.

 

Quote

I assume you replaced both mce.exe" and "Simco64_Ldr.exe

 

I did.

 

After extensive testing I finally found a reliable way to recreate this issue of the erratically opening doors, at least on my system:

 

The problem apparently is connected to the "Nav lights on" command.

When I don't use this command (but handle the nav lights manually myself) everything is fine, no issue with the doors.

But whenever I use this command (verbally or as part of a voxscript) during the GSX boarding process (started via the Fenix EFB or via the GSX menu) or after connecting the jetway and thus opening the L1 exit, the issue with the erratic door openings occurs right at the moment when the GSX boarding is completed.

And I can stop the issue immediately by giving the command "Nav lights off". Commanding "Nav lights on" again, and the doors start opening again. Easily reproduceable on my system.

So this is the second part of the issue. "Nav lights on" somehow overrides the settings in the mce.ini to deactivate the auto door handling.

 

So apparently the issue I see is a combination of MCE handling the wrong doors and messing up the setting to auto handle the doors or not.

 

Edited August 18, 20241 yr by RALF9636

On 8/18/2024 at 1:55 PM, RALF9636 said:

I tried with this option set to 0 and found that MCE opened the Overwing Emergency Exit instead of the FWD Cargo door and the R1 exit instead of the AFT Cargo door.

So this is the first part of the issue.

 

AFAIK Fenix automatically handles the doors when you load the aircraft via the "GSX" option in the EFB of the Fenix. Nevertheless I do see the issue also when I use the "Instant" option in the EFB and handle GSX via the GSX menu and the Fenix doors manually via the EFB. So that doesn't make a difference.

 

I did.

 

After extensive testing I finally found a reliable way to recreate this issue of the erratically opening doors, at least on my system:

 

The problem apparently is connected to the "Nav lights on" command.

When I don't use this command (but handle the nav lights manually myself) everything is fine, no issue with the doors.

But whenever I use this command (verbally or as part of a voxscript) during the GSX boarding process (started via the Fenix EFB or via the GSX menu) or after connecting the jetway and thus opening the L1 exit, the issue with the erratic door openings occurs right at the moment when the GSX boarding is completed.

And I can stop the issue immediately by giving the command "Nav lights off". Commanding "Nav lights on" again, and the doors start opening again. Easily reproduceable on my system.

So this is the second part of the issue. "Nav lights on" somehow overrides the settings in the mce.ini to deactivate the auto door handling.

 

So apparently the issue I see is a combination of MCE handling the wrong doors and messing up the setting to auto handle the doors or not.

 

Thanks for the detailed description.

Please try the new patch uploaded today

 

On 8/21/2024 at 10:42 PM, FS++ said:

Thanks for the detailed description.

Please try the new patch uploaded today

 

Seems to work fine now. MCE is not interfering with the doors on the Fenix any more.

Two things I noticed flying the Fenix A321:

1. MCE reads the correct values from the FMC into the Monitor page of the MCE UI, but the speed callouts on takeoff (100kts, V1, VR) come about 10 kts too early (also on the A319, I haven't checked the A320).

2. MCE does not take into account that the A321 has higher speed limits for the flaps than the A320 and so the FO moans about speed too high when he shouldn't:

Flaps 1: 235 (A319/A320: 230)

Flaps 2: 215 (A319/A320: 200)

Flaps 3: 195 (A319/A320: 185)

Flaps 4: 190 (A319/A320: 177)

Regards!

 

Edited September 29, 20241 yr by RALF9636

delete

Edited September 29, 20241 yr by RALF9636

20 hours ago, RALF9636 said:

Two things I noticed flying the Fenix A321:

1. MCE reads the correct values from the FMC into the Monitor page of the MCE UI, but the speed callouts on takeoff (100kts, V1, VR) come about 10 kts too early (also on the A319, I haven't checked the A320).

2. MCE does not take into account that the A321 has higher speed limits for the flaps than the A320 and so the FO moans about speed too high when he shouldn't:

Flaps 1: 235 (A319/A320: 230)

Flaps 2: 215 (A319/A320: 200)

Flaps 3: 195 (A319/A320: 185)

Flaps 4: 190 (A319/A320: 177)

Regards!

 

Thanks for feedback.

You can do it yourself.

Because Windows won't let you edit files in C:\Prohgram Files (x86)\ folder, go to C:\Program Files (x86)\Multi Crew Experience\Reference\ folder, copy "A320_ref.txt" file to desktop or other location, edit it in Notepad to correct the flaps detents values, then overwrite the file in reference folder.

Check it out with both A321 & A320, then when happy with it, send it to support so we can distribute it with the default package and you won't have to overwrite the file on each update.

As for the callout, it's a tough one. 

Unless you keep bombarding the sim every millisec to read the actual speed like mad and kill the overall performance in doing so, the implementation calls for a read once a second, then FO is allowed to make the call when within 2 knots of the target value. The result, sometimes  a couple knots two early, other times could be 2 knots too late, the callout itself lasting 2 seconds.

If it happens too often, please notify and we'll look at it closely.

Keep in mind MCE is reading the actual flight simulator indicated airspeed value (not Fenix displayed value) and it's not impossible the plane itself to be occasionally late on updating the value in PFD, because of some processing issue. This plane has no less than 4 external processes running at high priority.

By the way, this is why dialling FCU HDG, ALT VS is relatively slow on this plane (compared to PMDG 737 or 777. You have to add delays between two consecutive increment/decrement events or the plane is too slow to update the values, eventually overshooting/undershooting the target value if you do it too fast.

 

 

Thank you

 

21 hours ago, FS++ said:

Thanks for feedback.

You can do it yourself.

Because Windows won't let you edit files in C:\Prohgram Files (x86)\ folder, go to C:\Program Files (x86)\Multi Crew Experience\Reference\ folder, copy "A320_ref.txt" file to desktop or other location, edit it in Notepad to correct the flaps detents values, then overwrite the file in reference folder.

Check it out with both A321 & A320, then when happy with it, send it to support so we can distribute it with the default package and you won't have to overwrite the file on each update.

I changed this section

[FLAPS_MAX_SPEEDS]
1=235
2=215 
3=195
4=190

in the files

A321_ref.txt

A321S_ref.txt

AirbusA321_ref.txt

But MCE still complains "Speed to high" when going to flaps 2 at 210 kts.

Can I see somewhere which ref.txt file MCE uses for the current aircraft?

For the A320 MCE recognizes the correct speeds, so complains with flaps 2 at 201 kts but accepts it at 199 kts, so this does not seem to be reated to the following issue:

 

21 hours ago, FS++ said:

Keep in mind MCE is reading the actual flight simulator indicated airspeed value (not Fenix displayed value) and it's not impossible the plane itself to be occasionally late on updating the value in PFD, because of some processing issue. This plane has no less than 4 external processes running at high priority.

 

Indeed it seems it is a Fenix issue. I monitored IAS (on the PFD) and GS (on the ND) during the takeoff run and there are some discrepancies (wind included of course). The MCE callouts are correct when I calculate IAS from GS and wind. The IAS indication in the Fenix seems to be lagging behind a little.

 

Edited October 1, 20241 yr by RALF9636

So I also changed the flaps speeds in the A320_ref.txt and A320S_ref.txt files and now MCE uses the correct flaps speeds in the A321. But now obviously theses speeds would also be used in the A320 (which would be wrong). MCE seems to use the same ref.txt file for both the A320 and the A321 (and presumably also the A319).

 

5 hours ago, RALF9636 said:

So I also changed the flaps speeds in the A320_ref.txt and A320S_ref.txt files and now MCE uses the correct flaps speeds in the A321. But now obviously theses speeds would also be used in the A320 (which would be wrong). MCE seems to use the same ref.txt file for both the A320 and the A321 (and presumably also the A319).

 

Correct.

In MSFS, "A320_ref.txt" handles A320/A321/A319 so it's the only file that requires editing.

As said before, MCE reads indicated airspeed directly via Simconnect (no Lvar nor FSUIPC are involved) and somehow the plane isn't in synch with that speed.

The only way you can solve this on your side is..

Add 10 knots to all speed limits in ref file to prevent objections regarding flaps extension.

When inserting Vspeeds, add 10 knots to each entry (because MCE makes call-outs based on those). Or insert correct values in CDU, and in MCE monitor panel, add 10 knots to each (but then, they will be overwritten with those fetched from CDU). Eventually a new option can be added to stop getting data from CDU.

 

5 hours ago, FS++ said:

Eventually a new option can be added to stop getting data from CDU.

 

Probably not necessary. The issue only occured since one of the latest updates of the Fenix. Previously the IAS indication was correct. So obviously this is a new bug in the Fenix and I'm sure they will fix it.

On 10/2/2024 at 4:08 PM, FS++ said:

 

As said before, MCE reads indicated airspeed directly via Simconnect (no Lvar nor FSUIPC are involved) and somehow the plane isn't in synch with that speed.

 

It seems this is related to the "Sync Displays" option in the Fenix app. After activating this option the MCE callouts are again roughly in sync with the IAS indication on the PFD.

 

Edited October 3, 20241 yr by RALF9636