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 Dash8 Q400 v2 profile

I've updated the profile for the Q400 with some suggestions from people who use it. 

Some of the biggest changes are:

- Bespoke events to control radio  stack
- fixed missing NAV (LNAV) button
- The unused speed dial is now used to set the speed bugs for the captain's side
- Fixed an issue with LED's being on that shouldn't have been in some situations

Please see the readme before you jump in. If you have any questions or suggestions feel free to ask.




Steve McNitt

Comments

  • Hi Slayer,
    Just being cautious.
    I assume I can install v2 over top of v1?
    Will this result in the duplicate entries? I then delete all the duplicate entries one by one?
    Will I lose the bespokes that I have created on my own?
    For the radios; are these bespoke events for the radios so we can set them up how we like? Or are they all set up the way you explained to me awhile back?
    Thanks for your HUGE contributions!
    Dave

  • Keep what you have. You would loose your custom stuff like the radios. You've already done most of the things I put in this version
    Steve McNitt
  • Perfect. Was wondering if it was worth the change for me.
    Thanks again,
    Dave
  • No problem. 

    The biggest issue was the missing Lnav which you kindly pointed out. This is mainly for those who are just using a stock version of what I initially made available or for someone new. If you have spent a bunch of time customising it to your particular hardware then I advise against updating. 


    Steve McNitt
  • Thanks once again for your efforts.
    Have downloaded and installed the latest version and note the following.

    On the MCP pressing the speed button brings up 30 and IAS 30 on the PFD.  Rotary on the MCP does not change these values,( it used to). V!, V2 etc work when the rotary is pressed.

    V speed on the thumb wheel. When operated on the MCP the corresponding wheel on the Dash rotates, but no display  changes on the MCP or PFD.

    Press VS on MCP and "VS" appears on the PFD, but no MCP function. ( Have checked wheel operates with 737).  Use wheel on the Dash , then display on both PFD and MCP.

    Using the latest GIT. Win7 64bit and P3D V3

    Probably finger trouble but help appreciated.

    Regards  Roger Hollands
  • Hi Roger. On the previous version I mistakenly left the speed rotary at the default setting because I hadnt programmed anything to it yet.

    On the Dash 8 the pitch wheel will set the speed and the vertical speed. I set it up on the MCP Pro to operate like it does in the virtual cockpit.

    First press the VS button then use the pitch wheel to adjust the vertical speed or press the IAS button and also use the pitch wheel to set the speed. This is backwards compared to the 737 but thats how it works on this aircraft. All I did was map the pitch wheel in the dash to the vs wheel on the mcp, the rest of the logic is in the majestic already.

    The speed/mach display still indicates the speed setting but the rotary below it wasn't needed because speed is set through the pitch wheel so I decided to use it to set the reference speed bugs [V1 V2 Vr Vrfi etc.]

    There is nothing on the mcppro that shows the values, you will still have to refer to the left PFD in the VC or 2d window.

    To set reference speeds, momentarily push in the speed knob, set v1, push again , set v2 etc

    There is an included .jpg file in the profile to illustrate the buttons etc
    Steve McNitt
  • Thanks for prompt reply.

    Your .jpg is most helpful.

    The problem I have is that the wheel on the MCP and the Dash are linked, but in IAS or VS mode I have to use the wheel on the Dash to adjust the values.  Once the wheel on the Dash is rotated, then the approprate display on the MCP is activated.

    As most things work do you think it worth re downloading the files and try again.

    Regards  Roger H
  • Very strange indeed. Yes, please try a fresh download, this time and try this:

    Reset the profile for the MCP first to FS default, then go into detective and click the red x to clear out all bespoke events. Then import the new bespoke events and finally import the MCP profile again and see if it is working. 
    Steve McNitt
  • Tried all the above. Still the same.

    What is odd I have plugged in an old Saitek AP panel and IAS and VS can be set from it.  The MCP and PFD and Saitek  all sync together.  Unpluged Saitek and back to the situation where info is received from the PFD but none is sent back from the MCP  for those two functions.  Will put the Saitek panel back to good use.

    Roger
  • edited April 2016
    Sounds like some kind of conflict with the pitch wheel. I haven't had any other reports of this yet and that function hasn't changed since the first version.

    Have you double checked that your MCP is set to "compatible addon" within GFconfig?

    One last ditch thing you could try too for the VS wheel is setting clockwise to: AP_VS_VAR_INC and CCW  to AP_VS_VAR_DEC   I believe those are the default simcconnect variables that the saitek would also hook into.  I know some of the default stuff worked on the Dash 8 just can't remember if that did . Seems like I could set VS but not speed...can't remember for sure.
    Steve McNitt
  • Off to the sun for a week or so.  Will try again later.  Many thanks for your support.

    Roger
  • edited April 2016
    FYI, I'm filling in the Q400 Pro mouse event blanks on Steve's google sheet ... it's a VERY tedious process and will take some time ... hope to get them all done within the next couple of weekends.  I've added about 30-40 functions so far in my hunting.

    EDIT: if someone has already done this for all the events (over 500), please let me know and I'll stop NOW!  I asked Oley/Simeon for a list, but they never got around to it.

    Cheers, Rob.
  • It is indeed tedious especially when you sometimes don't see what is working
    Steve McNitt
Sign In or Register to comment.