Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Feedback on Fenix A320

Featured Replies

So I've finally finished translating an airline's procedures for the A320 into MCE scripts for use with the Fenix A320. I know this is still in beta and WIP so expectedly some things don't work yet. Here's a list of what I found.

Commands that exist but don't work with Fenix yet:

  1. Spoilers disarm (needs to be commanded twice to actually disarm; lever pops back up initially)
  2. Instrument brightness adjustments
  3. Closing/opening windows
  4. Your ND mode set to arc (ND is set to VOR instead)
  5. Your ND range to three hundred twenty (no action)
  6. Your ND show terrain (controls Captain's setting)
  7. Reset rudder trim (no action)
  8. F/O flight control check (no action)
  9. Your EFIS show VOR (no action)
  10. TCAS control (the switch on the right of the panel, not ATC)
  11. Dome lights
  12. Oxygen check (not sure if possible since the lid has to be opened first)

Commands that don't exist (probably for any Airbus) but would be nice:

  1. Full control of the center clock
  2. F/O using the chronometer on his side instead of the Captain's
  3. Tray tables opening/closing independently
  4. Altitude reporting switch operation
  5. ATC (transponder) control
  6. MCDU: Up and down buttons
  7. APU master switch on and off independently of APU start switch

I've also noticed that some of the push buttons are set to on and off correctly (lights go on and off) but the button itself often gets stuck pressed-in. Also, I usually get a notification from the F/O just after MCE launch that we "just lost the nav radio".

Edited by threegreen

  • Replies 44
  • Views 6k
  • Created
  • Last Reply
  • Commercial Member
49 minutes ago, threegreen said:

So I've finally finished translating an airline's procedures for the A320 into MCE scripts for use with the Fenix A320. I know this is still in beta and WIP so expectedly some things don't work yet. Here's a list of what I found.

Commands that exist but don't work with Fenix yet:

  1. Spoilers disarm (needs to be commanded twice to actually disarm; lever pops back up initially)
  2. Instrument brightness adjustments
  3. Closing/opening windows
  4. Your ND mode set to arc (ND is set to VOR instead)
  5. Your ND range to three hundred twenty (no action)
  6. Your ND show terrain (controls Captain's setting)
  7. Reset rudder trim (no action)
  8. F/O flight control check (no action)
  9. Your EFIS show VOR (no action)
  10. TCAS control (the switch on the right of the panel, not ATC)
  11. Dome lights
  12. Oxygen check (not sure if possible since the lid has to be opened first)

Commands that don't exist (probably for any Airbus) but would be nice:

  1. Full control of the center clock
  2. F/O using the chronometer on his side instead of the Captain's
  3. Tray tables opening/closing independently
  4. Altitude reporting switch operation
  5. ATC (transponder) control
  6. MCDU: Up and down buttons
  7. APU master switch on and off independently of APU start switch

I've also noticed that some of the push buttons are set to on and off correctly (lights go on and off) but the button itself often gets stuck pressed-in. Also, I usually get a notification from the F/O just after MCE launch that we "just lost the nav radio".

Thanks for the list. They should be sorted this week.

By the way, FO can rotate SPD, HDG, ALT and VS now. It's just that we don't let him do that until he is able to read the actual windows values at any given time, without needing to give instructions such as "Set them to zero" so MCE can make assumptions and never touch them manually which would be silly.

 

  • Commercial Member
On 8/16/2022 at 6:11 PM, threegreen said:

So I've finally finished translating an airline's procedures for the A320 into MCE scripts for use with the Fenix A320. I know this is still in beta and WIP so expectedly some things don't work yet. Here's a list of what I found.

Commands that exist but don't work with Fenix yet:

  1. Spoilers disarm (needs to be commanded twice to actually disarm; lever pops back up initially). Should be sorted
  2. Instrument brightness adjustments.... Done "pfd on/off", "nd on/off", "upper eam on/off" etc..
  3. Closing/opening windows
  4. Your ND mode set to arc (ND is set to VOR instead)... Should be OK
  5. Your ND range to three hundred twenty (no action)... Should be OK
  6. Your ND show terrain (controls Captain's setting)... Corrected
  7. Reset rudder trim (no action)....Should be OK
  8. F/O flight control check (no action)
  9. Your EFIS show VOR (no action)
  10. TCAS control (the switch on the right of the panel, not ATC)... Both transponder mode and TCAS mode should work as expected
  11. Dome lights     .... Sorted
  12. Oxygen check (not sure if possible since the lid has to be opened first).... FO does that now

Commands that don't exist (probably for any Airbus) but would be nice:

  1. Full control of the center clock
  2. F/O using the chronometer on his side instead of the Captain's.... Sorted
  3. Tray tables opening/closing independently... Implemented separate control
  4. Altitude reporting switch operation... Not sure I understand twhat you mean by this
  5. ATC (transponder) control  .. Both transponder mode and TCAS mode should work as expected
  6. MCDU: Up and down buttons
  7. APU master switch on and off independently of APU start switch... Should be sorted

I've also noticed that some of the push buttons are set to on and off correctly (lights go on and off) but the button itself often gets stuck pressed-in. Also, I usually get a notification from the F/O just after MCE launch that we "just lost the nav radio".

Get the patch

http://www.multicrewxp.com/Latest-Beta.zip

See embedded notes above

  • Author
21 hours ago, FS++ said:

Get the patch

http://www.multicrewxp.com/Latest-Beta.zip

See embedded notes above

Great to hear, thank you! I'll report back when I've had the chance to test.

What I mean by altitude reporting is the switch on the transponder panel.

  • Author
On 8/20/2022 at 10:01 PM, FS++ said:

Get the patch

After testing I found the following:

  • Only one oxygen system is tested and the lid is left open
  • Your ND mode to arc still goes to VOR
  • Center clock: F/O won't reset the clock, start clock puts it into stop rather than run
  • No control for the ATC switch (left upper switch on transponder panel)
  • Your side show terrain still actions the Captain's button
  • APU master switch has no command (I used "APU master on/off)
  • Spoilers still need to be disarmed twice
  • Rudder trim reset not working
  • PFD and ND on/off may be better if it only controls the F/O's instrument rather than the Captain's too

The other items work fine now, thanks.

  • Author
3 hours ago, FS++ said:

Are you by any chance using hardware spoilers? And possibly set to react to some events coming via FSUIPC? Thanks

No, none. I just arm the spoilers with the mouse in MSFS and then test the command. On the first try the lever is pushed down only a little and pops right back up, on the second try it works as expected. A workaround might be adding the command twice to the script.

  • Commercial Member
On 8/25/2022 at 8:12 PM, threegreen said:

No, none. I just arm the spoilers with the mouse in MSFS and then test the command. On the first try the lever is pushed down only a little and pops right back up, on the second try it works as expected. A workaround might be adding the command twice to the script.

Grab the nest patch (same link)

Spoilers disarm should be sorted.

Almost all little imperfections mentioned earlier should be sorted.

I guess you are concerned about Fo potentialy switching PFD OFF and ND on you while you are on final. While he will happily switch them ON without warning, he'll never switch them off by accident.

Also in this patch, we have a breakthrough with FCU as dialling SPD, HDG, ALT and VS is finally possible.

Make sure you replace/add all files.

Starting from now, the default checklist assigned to Fenix A320 is the one displayed in EFB.

 

Edited by FS++

  • Author
20 hours ago, FS++ said:

Almost all little imperfections mentioned earlier should be sorted.

Sounds good, thanks!

20 hours ago, FS++ said:

I guess you are concerned about Fo potentialy switching PFD OFF and ND on you while you are on final. While he will happily switch them ON without warning, he'll never switch them off by accident.

I just didn't understand why he would switch off my side instruments too rather than only his. I'm thinking about this form a real world perspective where both pilots have their area of responsibility and the F/O wouldn't touch the Captain's stuff unless specifically instructed, while in case of instrument brightness he wouldn't even be able to reach the knobs from his position. Same thought with the chronometer. Now that the F/O uses his side chronometer I can script him tracking the 3/5 minute warm-up times for the engines while I use my chronometer for other things.

20 hours ago, FS++ said:

Also in this patch, we have a breakthrough with FCU as dialling SPD, HDG, ALT and VS is finally possible.

Neat!

  • Author
On 8/27/2022 at 11:04 PM, FS++ said:

Grab the nest patch (same link)

The "your ND mode to arc" still sets it to VOR. There's also still no independent control for the APU master, correct? Also, the transponder control isn't right. What I meant was control over the ATC switch in the upper left corner of the transponder panel. The altitude reporting switch works now in conjunction with the TCAS control which is good, but ATC is still needed to actually switch the thing on. The other items work perfectly.

  • Commercial Member
On 8/31/2022 at 7:11 PM, threegreen said:

The "your ND mode to arc" still sets it to VOR. There's also still no independent control for the APU master, correct? Also, the transponder control isn't right. What I meant was control over the ATC switch in the upper left corner of the transponder panel. The altitude reporting switch works now in conjunction with the TCAS control which is good, but ATC is still needed to actually switch the thing on. The other items work perfectly.

That will be taken care of in next update.

Meanwhile, we had to upload the new patch as it gives FO insight into the CDU PERF page so he can be in synch with Vspeeds and you won't need to input them into MCE UI. MCE will have the values roughly 40 to 50 seconds after most of the data data has been entered into CDU.

Just redownload:

http://www.multicrewxp.com/Latest-Beta.zip

In this patch it's also posible to ask FO to set a specific pitch trim, not to mention reset it to zero

Set pitch trim down two decimal one

elevator trim one point five up

reset pitch trim

... Obviously, many other variations are available

 

Edited by FS++

  • Author
1 hour ago, FS++ said:

That will be taken care in next update.

Meanwhile, we had to upload the new patch as it gives FO insight into the CDU PERF page so he can be in synch with Vspeeds and you won't need to input them into MCE UI. MCE will have the values roughly 40 to 50 seconds after most of the data data has been entered into CDU.

Just redownload:

http://www.multicrewxp.com/Latest-Beta.zip

In this patch it's also posible to ask FO to set a specific pitch trim, not to mention reset it to zero

Set pitch trim down two decimal one

elevator trim one point five up

reset pitch trim

... Obviously, many other variations are available

Nice! Keep the updates coming 😝.

  • 3 weeks later...
  • Commercial Member
On 9/1/2022 at 6:38 PM, threegreen said:

Nice! Keep the updates coming 😝.

Sorry for the delay. Mostly due to integration with Simbrief as well as attempting to get FO to "see" FMA modes as they change.

Get the patch and make sure all files are replaced, and some added.

http://www.multicrewxp.com/Latest-Beta.zip

Eventually copy and paste the link to browser address bar as it seems not easily accessible from forum.

 

 

 

 

Edited by FS++

  • Author
17 hours ago, FS++ said:

Sorry for the delay. Mostly due to integration with Simbrief as well as attempting to get FO to "see" FMA modes as they change.

No worries. 

What does simbrief integration entail?

Also, I just clean installed W11 on my system and need to reinstall MCE. I'm not sure where to get the installer and if that includes the latest betas. Or can I use the older installer I still have and just install the latest beta over it? I seem to remember something about needing to be on a certain version in order to apply new patches; I think my installer is too old for that.

  • Commercial Member
52 minutes ago, threegreen said:

No worries. 

What does simbrief integration entail?

Also, I just clean installed W11 on my system and need to reinstall MCE. I'm not sure where to get the installer and if that includes the latest betas. Or can I use the older installer I still have and just install the latest beta over it? I seem to remember something about needing to be on a certain version in order to apply new patches; I think my installer is too old for that.

Just head to the website to download latest release V2.9.8.0

http://www.multicrewxp.com

Then get the Beta patch and replace/add files as per folder structure.

The Beta is mostly for deeper FENIX A320 integration as well as Simbrief functionality not available in release.

Simbrief integration means once MCE propmts for the Simbrief ID and you type it in, it will automatically fetch the latest flight plan so you won't need to browse and locate whatever_file.pln

Simbrief ID is then saved to "mce.ini" for future reference.

Info will be displayed in <ATC> tab and when you click <Flight Plan>, the route will be displayed. More info could be added at a later stage as users see fit.

It can be useful for airplanes that don't have EFB yet.

 

Edited by FS++

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.