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.

FlightFactor A320 Ultimate

Started working on a profile for FFA320 ultimate beta, EFIS and MCP only for now. If anyone else has good progress already on this let me know other wise I'll continue.
Steve McNitt

Comments

  • I am very happy to test any release you may have for the 320. Thank you Jon
  • Ok this profile will take me a bit longer to complete as it looks like there are no native datarefs to access in this aircraft. I found a plugin that will hopefully allow me to hook into it though and then out to GIT/GF stuff. Basically have to build 2 profiles to make it work 1 for the plugin and 1 for GIT.

    I'll post a test here when I make some progress.
    Steve McNitt
  • edited November 2017
    This is a very rough release NOT complete , lots of stuff is not implemented , if you don't want to test it and offer feedback/suggestions please wait until the final version. Only proof of concept at this point using commands that Mokney used for examples.

    Please see installation.txt on how to install as it is not a normal profile, an additional (free) plugin is required.

    Steve McNitt
  • edited December 2017
    How would you guys like to see the push/pull functionality of Airbus knobs handled? At the moment I'm just using the push. I've considered a few ideas such as a quick push would be the normal push function and and push and hold would be the pull. Possibly could use VNAV/LNAV buttons for managed modes too.

    Also the VS is a knob with push/pull on the Airbus but only a wheel with no push or pull on the Goflight MCP

    FD switches are another problem since they are momentary/toggle push buttons on an airbus so there is no real on/off - the "on" state is the button pushed in and the "off" state is when you release the button. If I only do an "on" the button sticks in and will cause a problem because the aircraft would think the button stuck. Maybe I can hit the avionics directly and come up with something.

    Lots of hurdles to do in this aircraft and progress is plodding along. I'll prob release another beta soon once I get the display blanking working properly for IAS, heading, Altitude and VS
    Steve McNitt
  • push/pull functionality of Airbus knobs handled? I've considered a few ideas such as a quick push would be the normal push function and and push and hold would be the pull.

    Sounds good to me, thanks for doing all the hard work btw.
  • edited December 2017
    New version with push/pull as discussed above, had to add a bit of logic so that it will not fire the quick push before the long push(pull). Some display blanking ( works but not quite right yet) Both FD and AT switches now working with indicator lights. Currently using the CWS buttons for the push/ pull feature of the VS knob. I haven't changed the EFIS since last version

    Still beta but getting closer. I'm not used to writing datarefs etc. so it takes so long because have to edit 3-4 files at once, with different syntax between them. One little typo can bring the whole house of cards down so to speak lol.
    Steve McNitt
  • As of Feb 1st 2018, I see that this aircraft has gone back on sale. Not sure if it's a full release or limited. I know with all of FF's other planes, they include daterefs and commands in DREDatarefs. Is this plane the same structure? Do we know? I'm thinking of picking it up and starting on my panels but I don't want to make a bad purchase and have mousefly when I have all of these wonderful panels to fly with.
  • Nope, no stock datarefs. Need to use a plugin from a guy named Mokney over at the .org and create all your own datarefs, then create a GIT profile based on that.

    the A320 was originally made as a trainer for real pilots and is being adapted to X-plane so it has its own program code outside x-plane. Maybe in final release FF will build in more datarefs outside what they put i to make it work with x-plane.
    Steve McNitt
  • well thanks for the info Slayer. That answers that. I'll stick with the boeings for now and hold out for that 777 coming down the pipe. By the way, I saw another group is nearing finishing their A319 and it looks sharp.

    Thanks again,
    Justin
  • Anyone know how I could go about getting the elevator trim on the lgt module to control pitch trim? Thanks
  • Don't think you can put trim on a rotary in the Airbus since its FBW trim inputs get sent to the computer(digital), the trim in the real thing is momentary switches not an axis like a Cessna where it is directly connected to the flight surface(analog).
    Steve McNitt
  • Slayer, would your FFA320 Ultimate GIT profile be also usable with TouLiss A319 ?
    Flakster
  • Oh, I just unzipped your file and see it requires the FFA320 Connector ..
  • The FFA320 Connector isn't available. Is there no chance to use my GF-MCP Pro with the FF A320 Ultimate?
    Very sad...
  • Now I found some versions of the FFA320 Connector, but if I use them the FF A320 doesn't work. The PFD and the other screens are green an I get an error message.
    Is there anything new information wether FF will make it possible to use GoFlight modules? It's a pity.

    Regards,
    Martin
  • Hmm I just updated the aircraft and put in the connector again I downloaded 1.16 from github and my screens are fine but on the bad side I forgot X-updater erases everything so I lost whatever was done between what is posted here and what I had :(

    Someone else had the problem of green screens too but can't remember the fix I believe a conflict with another plugin.
    Steve McNitt
  • Hi Steve,
    the green screen problem is solved. The xjet plugin from Airfoilab was the culprit. Now the screens are ok, but if I import the Zip file with the lvars for MCP-Pro and EFIS at the end there is an error that some function are not found.

    But my bigger problem is, that the first minutes the MCP-Pro and Efis work (unless the Baro rotary which decrease the baro does not work), but after a few minutes my other goflight modules (GF-45, P8, RP48, T8, SECM and LGTII) seem to lose the connection and are booting again and again. First I thought my USB Hubs where the problem, but if I delete the A320 connector and delete the settings in GIT all is working fine. Also with other planes I have no problems.

    Hope Flightfactor will make commands in future, which can be used easier with GIT and the GoFlight modules.

    Martin
  • Hey gang-

    I'm trying this out and absolutely nothing is working sadly. Any suggestions? Is it not feasible since their recent updates to use the MCP Pro with this bird?
  • Good morning from Germany,

    maybe i found a solution to get this A320 to fly with the MCP.

    I mapped all buttons/ knobs to keypress comands via the GoFlight tool, then set in Xplane via the connector plugin all AP mappings to key commands. This is the short story but it was a long shot.

  • Hi,
    Merry Xmas!
    And the digits at the MCP-Pro are working?
  • unfortunately not
  • Flight Factor has updated the software

    - Added a dataref for each action in cockpit that can be both monitored and written
    - Added commands to ALL functions in the cockpit that can be used on hardware
  • Any news on this plane? I saw that there are Datarefs available from Flightfactor. Is it now easier to make bespoke events for the A320?
    Also I want to set the landing lights with my SECM. But the commands I see in X-Plane, I don't find in GIT.
Sign In or Register to comment.