Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.

Go Flight MCP Pro for Airbus aircraft in MSFS

stevebarker12stevebarker12
in GoFlight Interface Tool - Technical Support
Will the interface tool work with Fenix A320 and MS/Asobo A320 neo default aircraft?

Comments

  • admin_ppsadmin_pps
    Technically the GoFlight Interface Tool works with all aircraft. However, the available functionality depends upon whether the aircraft developer has built the aircraft so it responds to Simconnect events and variables or exposes lvars and hevents.

    Searching the forum for Fenix, I found the following post of someone who had built support for the MCP and EFIS: https://www.pollypotsoftware.org.uk/vanillaforums/discussion/comment/10334#Comment_10334. I might be worth contacting the author to confirm those config files still work.

    I worked at interfacing the Asobo A320 about 18 months ago and it was a nightmare to do, and some functionality didn't work at all. Whether they have improved support for hardware interfacing since then, I do not know.

    Best wishes
    Steve
  • stevebarker12stevebarker12
    Ok thankyou.
  • fsamfsam
    Hi, first of all you have to "translate" the Boeing MCP into an Airbus FCU, meaning define what is the nearest to Boeings LNAV/VNAV, LVL CHG or managed / manual modes at the other side of the pond... a little help is the overlay for the GF MCPPRO for Airbus Style FCU available at flightsim.to. Then you can easily assign the fenix Lvars to bespokes, for example the EXPED Function (in my understanding of the systems nearest to LVL CHG) is S_FCU_EXPED +=2 or APPR is S_FCU_APPR +=2 and so on. It is working for the whole FCU/EFIS and most of the systems, well organized Lvars available via the GFIT Detective. Then you have to assign the Bespokes to your Switches and Buttons and add the respective lightfunctions e.g. for EXPED using I_FCU_EXPED / ON / 1 or for APPR I_FCU_APPR / ON / 1. As I said, it is working here - but the displays are still not supported as written in the referenced thread above, only E_FCU_XXX is given some respond, seen in the developer mode for the displays. For VS I'm using E_FCU_VS / Multiply as integer / 100 and for ALT I'm using E_FCU_ALTITUDE / Multiply as Integer / 1000 but only if the step size is set to 1000 and initial value was 0100. Unfortunately no other solution found. But again - the Fenix Lvars are well organized and easy to find with the help of the detective. Best regards Ralf
  • fsamfsam
    since last fenix update use of N_FCU_ALTITUDE / HEADING / VS / IAS for manual display modes is working, unfortunately I have no idea, how to blendout display if managed mode is pushed.
  • admin_ppsadmin_pps
    fsam said:

    since last fenix update use of N_FCU_ALTITUDE / HEADING / VS / IAS for manual display modes is working, unfortunately I have no idea, how to blendout display if managed mode is pushed.

    What do you mean by blendout?
  • fsamfsam
    sorry for late respond, meaning blanking display in managed mode and display values in manual mode. Best regards
  • admin_ppsadmin_pps
    Is there a variable that shows what mode its in?
  • fsamfsam
    no, not found so far, mode activation by means of S_FCU_HEADING as toggle (add 1 or subtract 1) and HDG value manual increase/decrease is with E_FCU_HEADING (incr/decr), indication then is N_FCU_HEADING. I think, it's straight from ProFlight wich is in use by Fenix as system software. If I could find a status variable for managed/manual mode - how can I blank the display with the help of it? Thank you and best regards
  • admin_ppsadmin_pps
    fsam said:

    no, not found so far, mode activation by means of S_FCU_HEADING as toggle (add 1 or subtract 1) and HDG value manual increase/decrease is with E_FCU_HEADING (incr/decr), indication then is N_FCU_HEADING. I think, it's straight from ProFlight wich is in use by Fenix as system software. If I could find a status variable for managed/manual mode - how can I blank the display with the help of it? Thank you and best regards

    Use a Bespoke Variable for the display which is set via a Start Bespoke Event (continuously runs) which would check the mode variable and set the Bespoke Variable value as applicable. To blank the display, set the Bespoke Variable to some out of range value that would never appear on the aircraft display and configure the display to use BLANK_EQUALS with the out of range value.

    Best wishes
    Steve
  • fsamfsam
    Hello Steve, thank you for this input, will try it out with the blank_equals out of range method. Best regards Ralf
Sign In or Register to comment.

© Vanilla Keystone Theme 2025