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.

Q400 Download

dave39dave39
in GoFlight Interface Tool - Technical Support
Hi,
Life took me away from my hobby for a bit and I see that Slayer has a new Q400 download.
Looking at the .jpg for the EFIS/MCPPRO that the key assignments are the same as mine. I am still
successfully using the previous version and am wondering if updating to the new one is
worthwhile for me?
Somewhere along the way I read something about speeding up the rate at which the knobs on
the MCPPRO could be turned without locking up. Is this in there too?

Should I "fix it if it ain't broke?" :-)

Regards,
Dave

Comments

  • SlayerSlayer
    Hi, here is the changelog for the last one I released:

    18 APR 16
    - Re export with new version of GIT 2.1.19.5
    - Added missing light switch designation to .jpg file
    - Added bespoke events for radios to use with GF-166
    - New button layout .jpg
    - MCP LNAV button = NAV button and the MCP VORLOC button = BC( not sure how this slipped by )
    - CORRECTED: the APP button light was turning on as well as the AT LED with no light data set
    - Added bespoke events for using the left and right NAV source selectors with a rotary dial (MJC_AFCS_NAVSRC_*)
    - Added Bespoke events for TOGA and AP disconnect to use with a yoke
    - speed dial on MCP now used for setting speed bug on captains side(because the pitch wheel sets the speed already)


    19 MAR 16
    - Include 2 GF166 profiles for NAV radios and VHF (VERSION 2.2.4.1 or greater required)
    - Rework HDG, CRS1 and CRS2 knobs to turn faster
    - File naming acording to new version

    21 MAR 16

    -Re-exported files again some changes were not present (they were on my system but didn't go into the export)


    If you don't care about any of those fixes stick with the old one.

     GIT has improved a lot too in the meantime. There is a new method for access to the Q400 but unfortunately I would have to redo the whole profile from scratch because you have to use the old method or the new one and can't mix the two. 

    I might remake it but no promise on a timeline
    Steve McNitt
  • macwinomacwino
    Steve, I'm new to GIT and need some clarification about how one imports your Q400 files.

    If I'm reading your comments above correctly, you seem to suggest that one ought to use the pre-v2.5 import method which involves extracting the various xml files from the Zip, and then importing them in the order specified in the User Guide and your Read Me using the Detective screen for the <aircraft>.xml and the Device screens for the device specific xml files. 

    Where I'm confused is that both your Q400 and Rob's A320 packages also have an xml file of a type not mentioned in your Read Me or in the User Guide. This is the file named mjc8q400 Vars.xml in your Q400 package and the file named BespokeVariables.xml in Rob's A320 package. 

    At what point in the process are these files supposed to be imported?

    Thanks,
    Robert
  • admin_ppsadmin_pps

    Hi Robert,

    The "<aircraftname> Vars.xml" is imported automatically when Bespoke Events are imported.

    I do not know why Rob included BespokeVariables.xml - perhaps it was from an earlier version where the Vars could not be exported. Unless there is anything in that file it can be ignored, otherwise copy and paste the contents into your own BespokeVariables.xml.

    Best wishes

    Steve

  • dave39dave39
    Hi,

    I am not sure what happened, however as a result of having to move my computer and thus unplugging all usb's etc., I seem to have lost the MCPRO and EFIS setups that I had downloaded and imported in to GIT. I also updated to the latest GIT 2_5_1_0 which probably didn't  helped matters. So before going ahead with importing I have to delete all the existing bespoke events prior to starting the procedure, correct?

    What I am wondering is if I can somehow keep the events that I created myself? I realize that clicking the red X in the bottom right corner deletes everything and I am trying to avoid that. While it might be time consuming can I delete them one by one, so I don't lose the ones I want to keep?? Or, is there an easier way??
    Thanks,
    Dave

  • admin_ppsadmin_pps

    Hi Dave,

    If the Bespoke Events are still present, leave them be. Simply load the configs for the MCP PRO and EFIS on the relevant tabs and you will loose nothing.

    Best wishes

    Steve

  • dave39dave39
    Thanks for the quick response Steve.

    The bespoke events that are there have no code in them. Is that normal?
    Do I have to import the mjcq400.xml if i want to add the GF166 which I didn't have before?
    Difficult to know what to do when I don't understand the mechanics of how this works.

    Can I manually delete the bespoke events that I didn't create and exit the software to save it, Then start with importing the mjcq400.xml and then do the specific imports in each tab.

    Thanks for your help.
    Dave
  • admin_ppsadmin_pps

    Hi Dave,

    If you want to install the GF166 then your best bet would be to manually delete the Bespoke Events which are not yours then run the Import Wizard on the front screen and it will do everything for you - just tick what you want to install.

    Best wishes

    Steve

  • SlayerSlayer
    I included profiles for both radios like we had set up before
    Steve McNitt
  • dave39dave39
    I noticed the new "Install Wizard" but haven't done and reading yet to figure out how to use it. If it's that easy, I'll try it!

    thank you gentlemen
  • dave39dave39
    Well that sure worked well !!!!!!!! Imported efis, mcppro and one 166.
    Only hiccup is that the wizard only gave me the option to select one 166 and it imported the VHF as device 0. The other 166 tick boxes were greyed out.
    Tried importing the mjc8q400_GF166-NAV as device 1 on its own, and it populated fields, but didn't bring either of my remaining 166's too life. (Have 3 in total)
    Any ideas would be great!
    Thanks,
    Dave
  • admin_ppsadmin_pps

    Hi Dave,

    You will have to pick the GF166 device you want to configure on the GF166 tab and then click import and select the correct GF166 config you wish to use.

    Best wishes

    Steve

  • dave39dave39
    Hi Steve,
    Been fooling around with it for a few days and no luck. As outlined above, I can't get the second 166 to come to life. I can see that the import worked into device 1 but nothing lights up on my 166.
    Have UHF working on device 0 from original import with the wizard.

    Any suggestions??
    Thanks
    Dave
  • admin_ppsadmin_pps
    edited July 2016

    Hi Dave,

    I have just tried it with a clean config for the Q400 as follows:

    Import Wizard, selected MCP PRO, EFIS, GF166. Imported all OK and the GF166 Device 0 was picked up as the VHF.

    I then went to the GF166 tab, selected Device 1, clicked Import and selected the file mjc8q400_GF166-NAV.xml from My Documents\GoFlight Interface Tool\Temp. Enabled the device and everything was OK.

    Best wishes

    Steve

Sign In or Register to comment.

© Vanilla Keystone Theme 2025