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 pro & MCP PRO

Hello all
Seriously out of my depth with this at present, can anyone take pity on me and provide a basic setup for the above, got the q400 files from the downloads area but no lights work, wondered if its because I have the pro version.
I did note that a number of people were working on this, did it prove to be unachievable? If so please let me know, thanks

Comments

  • MCPPRO and EFIS setup done by Steve is the last item on the menu page.

    dave
  • have you used it successfully dave39? I ask because I didn't, I am sure its something I did but want to be positive
  • edited March 2016
    Most people forget to import the bespoke events. Once you do that it should work.

    Once the aircraft is running in the sim, open the detective and import(button on bottom of detective window) the file contained in the zip(mjcQ400.xml)

    I know it works on pro as that is the last version I created this using.
    Steve McNitt
  • Yes. I have both EFIS and MCPPRO and works well. Look at the .jpgs for functionality. Some poetic license was required as Slayer was trying to put a square peg through a round hole to get this to work.

  • Cliveparrot - is everything sorted now?

    Best wishes

    Steve

  • Yes I think so, need to test it as soon as time permits, displays fine but could not arm approach,
    as soon as I get some time i'll check it all out

    thanks ever so much for asking, hope your feeling better

    Clive
  • It works thanks, for some reason it doesnt work with the Dash 8 when using FSI Panel, when arming approach it just freezes the Dash in midair with all the warnings going off. The 777 does work with FSI Panel though, thanks for the help on the forum :-)

     

  • Checking the FSI Panel you need a registered version of FSUIPC for it to work with the Dash.

    Best wishes

    Steve

  • Hello
    I do have a registered version Steve
    Thanks very much
  • Hi Not sure what I'm doing wrong but I can't get the mcp pro to work with my majestic Q400. I get the Interface activated ok (3 green lights) and I imported mjcQ400.xml file ok when I opened the detective. Showing all zeros on MCP PRO and no buttons work. Will get back at this tomorrow, enough for tonight since I'm not getting anywhere. Any suggestions would be greatly appreciated. I did install 2.25.2 version of go flight drivers. Best regards Wayne
  • Hi Wayne,

    You load the xml file into Detective (Bespoke Events), then go to the MCP PRO tab and import the other file that configures your MCP PRO. Make sure you have GFConfig configured to a compatable add-on.

    Best wishes

    Steve

  • Hi Steve That is exactly what I did for both the mcp pro and Efis. When I push the mcp pro tab button the information appears to be all there in the drop down menus. I did have the altitude display and the heading display on the mcp pro working yesterday with the Q400 but the nav and app button light just stayed on and none of the buttons worked. I then decided to start again, now I have all zeros on the mcp pro and the mcp pro tab and Efis tab don't always work. Steve since I was tired and it was late last night when I sent you that message I forgot to mention that my Mcp Pro and Efis are already configured to the old original go flight interfaces that I installed 2 years ago and working very well. I have the goflight interface for the PMDG 737ngx and the goflight interface for the PMDG 777. Unfortunately as you know these interfaces will not work with the MQ400. I thought I might be able to install your interface in a separate folder for the Q400 and leave the old goflight interfaces to run my Efis and mcp pro for my 737 NGX and 777. When you have something working really well you hate to get rid of it. The old saying "if it ain't broke don't fix it" I thought applied. In spite of my problems installing your interface my old goflight interfaces continue to work well with my 737ngx and 777 so it's not affecting my old interfaces. So I'm thinking maybe my old goflight interfaces will also not conflict with yours. I do like flying the Q400 as well but I need your interface for that. What do you think, is it possible for me to do this or do I have to get rid of my old interfaces as well. Just afraid if I do that I won't be able to get anything working. I'm a old retired guy and not an expert with computers. I do have the registered version of FSUIPC. I have configured my 737ngx and 777 flight controls as well as the Q400 flight controls through FSUIPC using profiles. If you think this can't be done and the old interfaces are causing my problem then I won't waste any more of your time on this. Thank you for supplying this interface to the sim community. Thank you for your reply and time. Wayne
  • The GoFlight Interface Tool (GIT) is the successor to the GoFlight PMDG Interface product and supports the NGX and 77X in the same way. You can use GIT for everything and it should read in your old config files for NGX/77X. Having said that I'm not aware of any issue in running them all together.

    I'm no Q400 expert. Slayer wrote the config and is very helpful in getting it working for people. Wait for him to chip in as he has got it working for a couple of people with similar issues. There are a few recent threads on the Q400 have you checked them for assistance?

    Best wishes

    Steve

  • Yes I have, no luck but I will go over them again. Thanks Steve Wayne
  • edited April 2016
    As Steve said the new Goflight interface tool replaces the old Goflight PMDG interface it's basically  the same program just newer. Your T7 and 737 will work exactly like they did with the old version. If you are comfortable with the old version it is really similar.

    May I ask what hardware you are using or have configured that you are afraid will not work with the newer version of the software? 

    Steve would have to answer this but I'm not sure it's possible to have the PMDG interface and the Goflight interface tool both loading out of your dll.xml?

    I forgot to ask also if you have configured your hardware with GFconfig and set the MCPpro and EFIS to "compatible addon"  it might have changed if you installed the newer version like you said above. That would definitely make it not work  (I've done it a few times myself when I forgot to set it back after using the iFly)

    The Q400 only works with the newer GIT software , can't remember which version it was but fairly recent. Otherwise the lights and such will not work.

    If you don't have anything special configured and are just using an efis and MCPPro then it's really a painless upgrade to switch from the old software to the new. Even if you have configured stuff I think we could just export it and then load it into GIT.

    As far as FSUIPC and your controls nothing shouldn't be affected at all , this software really has nothing to do with axis assignments etc unless you enabled it


    Steve McNitt
  • Thank you for the reply. Your GIT is awesome. I found all my problems. As much as I tried to keep my old interfaces I was unsuccessful. I got your interface working fine with the MQ400 but it did interfere with the old interfaces I had installed. So I got rid of them and then found out that my PMDG 737NGX would not work with your interface. But that was my fault, last night I found out that I did not have the new update for the 737 NGX installed.

    I will download that today. The T7 works just fine. Your GIT works great as well with the Q400. The only thing that wasn't working was the vertical Speed Control. So I ended up creating a couple of macros with FSUIPC, one for a positive direction and one for a neg. direction. Just used the right and left click of my mouse on the Vert Knob to set this up. Does the job.

    So all good. Another thing I noticed was that the detective wasn't active with the 737ngx and the T7 but I didn't need to set anything up with these two aircraft it worked as soon as I installed your GIT.

    Anyway my worry was all for not regarding getting rid of my old interfaces. Yours is awesome.

    My hardware is as follows: Precison Flight Control Yoke, MCP Pro & EFIS, Saitek Throttle, Cessna Rudder Pedals, and I also have the Jetmax (Flight Deck Solutions) CDU. This is an awesome CDU, I would highly recommend it. Bit expensive but worth every penny. I'm using two monitors, 27' and 32".

    I learned a lot from your forum. You guys are great.

    Thanks again

    Wayne



  • I should clarify, in previous post I said both the 737 and T7 work with your GIT. The T7 did, I still need to download the new version update today for the 737. However I am sure it will work OK once I download that. It has a lot of the same stuff the T7 has on board and the T7 works great.

    All the Best

    Wayne

Sign In or Register to comment.