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.

Majestic Q400 EFIS and MCPPro profile

I've been working on this off and on for quite a while. Most of the stuff you expect to work does. Included is a .jpg to illustrate the control mapping.

Hopefully in the future I will add much more for others with more hardware than myself.

image
Steve McNitt

Comments

  • Great stuff. Can I add it to the downloads section of the website?

    Thx
    Steve
  • Sure, Thanks again for your great software
    Steve McNitt
  • Added. Thanks.
  • Sure  here is the updated version. re-exported 




    image
    Steve McNitt
  • Awesome thanks a lot!
  • Steve,

    Have you tried this file in P3D v3 as someone is having trouble loading it in?

    Thx

    Steve

  • I'm currently using  P3D v3.1
    Steve McNitt
  • edited February 2016

    Can you try renaming My Documents\GoFlight Interface Tool so your settings become unavailable for GIT and then try importing your profile for the Q400 and using it. You can obviously then delete the newly created My Documents\GoFlight Interface Tool and change the renamed one back to get your settings  back.

    Rob said the xml file needed CR/LF added to each line as he has had similar problems with another aircraft. The new version of GIT does that but it still appears that the problem remains.

    Appreciate your time on this as I don't have the Q400 installed at the moment.

    Thx

    Steve

  • I tried what you suggested that and it is working fine.

    I checked the files in the zip I sent you with Notepad++ and enabled the view for end of line symbos,  it shows CR/FLF after each line. Compared the 2 sets of files against each other and they look identical in size.

    Seems like I remember this problem happend to me before(not with this profile) but it errored on the first bespoke. It was either due to a corrupted file or  possibly a permissions issue...happened months ago and I can't remember exactly what the fix was.  Possibly it was when I had installed an upgrade version of Windows 10 and GIT started having weirdness like that crash he is having. A clean install of 10 solved all the niggling issues I was having with software. GIT wasn't the only thing (Avliasoft EFB was another unsolvable nitemare)


    Steve McNitt
  • Thanks for trying that. I'll let him know.

    Best wishes

    Steve

  • I am using 2.26.1 driver , could that be his problem?
    Steve McNitt
  • I'm not sure what it is. As I have said to Rob the export/input function hasn't changed in ages. We do now have P3D v3 deviating from the FSX standard and Windows 10 with its odd little bugs so who knows?!

    Best wishes

    Steve

  • edited February 2016
    I looked at Robs comments - especially the part where he said he may "revert"(implying he upgraded from Window 7?)  it jogged my memory and it mirrors the problems that I had when I had done the upgrade install from 7 to 10.

    While I'm no expert - from recollection I was looking at the .NET as the culprit, other people were having issues with programs that used .NET/ Windows 10 Upgrade - Something gets messed up when you upgrade from Windows 7 to 10, Since the 4.6 in included  with the OS all you could do was "turn on or turn off" Windows features and there was no way to fix it. 

    After struggling with several issues for the better part of a week I bit the bullet and did a clean install. I can't say I've had any Windows 10 / FSX/P3D addon issues since( and i have a TON of programs)  I know it's not what people want to hear but a clean Windows 10 install corrected all the problems for myself. 
    Steve McNitt
  • Thanks for the info. I have been baffled by some of the issues appearing lately and your explanation could be it. I didn't do an upgrade to Windows 10, I did a clean install as well and saw no issues.

    Thx

    Steve

  • edited February 2016

    What edition/version no. of the Q400 are you using Steve?

    Thx

    Steve

  • I'm using the pro version 1.018. Note that there was an additional download from majestic to update some files and that was 1.018b2 - Those are needed to make it work with P3D3.1. Downloaded that through the user area on their website. 
    Steve McNitt
  • I have the non pro version as well and that's what I started making the profile on but it hasn't been installed since I started using P3DV3
    Steve McNitt
Sign In or Register to comment.