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.

GF MCP Pro/GF Efis with Majestic Dash 8-Q400

13»

Answers

  • Martin1210Martin1210
    Ok, I tested and it doesn't work. If I turn the HDG rotary the values in the Dash Cockpit are ok, only the values at the MCPPRO doesn't work correct.
  • Martin1210Martin1210
    The same also after deleting the GIT folder in documents and a new import of the profile. Also I quit GIT correct. (but doesn't closed P3D with the running Dash). If I start GIT again, the problems are there.
  • admin_ppsadmin_pps

    This behaviour only happens with the Q400, all other aircraft work OK with GIT?

    Best wishes

    Steve

  • Martin1210Martin1210
    Did so, same situation. GIT have amnesia and did not save the MCPPRO data...
  • admin_ppsadmin_pps

    Sorry MArtin, I don't understand your last statement. Does this happen with all aircraft or just the Q400?

    Thanks

    Steve

  • Martin1210Martin1210
    Did so and installed into C:\Goflight. Same situation. GIT have amnesia and did not save the imported profile data from MCPPRO.
  • Martin1210Martin1210
    No this happens only with the Dash. With the A2A Cessnas I have no problems.
  • admin_ppsadmin_pps

    Martin, you are not answering my question.

    I understand that the Q400 with GIT is having "amnesia".

    Do you have the same problem with other aircraft such as the A2A C172 for example?

    Thx

    Steve

  • Martin1210Martin1210
    Sorry, I mean that I import the profile data from the MCPPRO and it works. If I quit GIT and start it again, it doesn't work. If I import the MCPPRO profile data again, it works. And this problem only occurs with the Dash. With the PMDG 737, 777, A2A C182 I have not those problems. I only import the profile data once and it works. Hope this explains this problem.
  • admin_ppsadmin_pps

    Hi Martin,

    OK. What I would like to do, is arrange to remotely control your PC so that I can check a few things and see the problem first hand.

    I won't be able to do this until Sunday afternoon. Let me know if you are happy for me to do this and I will email you directly with instructions for Sunday.

    Best wishes

    Steve

  • Martin1210Martin1210
    Hi Steve,

    this is ok. Normally I use Teamviewer for remote control. Sunday would be fine. Do you have my mailadress?

    Best wishes
    Martin
  • admin_ppsadmin_pps

    Hi Martin,

    Great. Team Viewer is also great. I can pick up your email from your forum account details. I will email you tomorrow with a time.

    Thx

    Steve

  • Martin1210Martin1210
    Ok Steve, the mail at the forum account is ok. I'll wait for you information. Now I'm off the computer and go to sleep.

    Best wishes and good night,
    Martin
  • SlayerSlayer
    Steve, the decimal problem was  on Martins machine when importing. In my files the decimals were there and also in the exported files.  I have tried to replicate it as well but I think it only happens because he is using German Windows?

    If you have the older version ( the one on the website)of my profile  can you please check it on his machine and then open the settings file and do a compare with notepad ++ you will see that all the decimals get removed. Kind of like the problem Microsoft had before with different countries using decimals and commas. I suspect it may be something related to conversions?

    I've since changed the bespoke events to get rid of the decimals,I had to use them to detect a state change to know if the dial was increasing or decreasing 

    The other troubling part is the heading thing,as it works perfectly on my machine. I only used the majestic hash codes and either increment by 1 or subtract by one. So somthing is getting lost here again in translation too.

    I have seen the problem Martin is having with it not saving before and I couldn't figure it out but for the life of me I can't remember how I got it to save finally. All I remember is that once it saved , everything worked fine after that and I figured it was a one off.....I did exclude every place GIT touched from Windows defender though and the .exe for it so I assumed that was what had corrected it.

    It also happened with the X-plane version and I made a post here about it when I was making the FF777 profile The error was caused because the bespoke events didn't save and the MCP had an empty bespoke event.

    As a result I always export my changes now before closing GIT for the night just in case.

    I would also like to help get to the bottom of this as it is a devious little bugger. 

    If you need you can do teamviewer on my machine too and I will show you the heading works perfectly. I'm totally at a loss on how 3 people can have different results with the same events but my gut tells me it is something to do with the differing language versions of Windows.

    Steve McNitt
  • Martin1210Martin1210
    Good morning,

    just want to say that I'm using the MJC Dash Pro Edition v1.018c.

    Yesterday I made another test. If I start P3D, load the default flight, start GIT and switch to the Dash I get those errors for every bespoke event. I posted one of those error screenshot above. At this moment I have to click the OK button for every error in the message Then I have to delete every bespoke events in detective. The red X to delete the bespoke events doesn't work anymore. This behavior happens everytime I switch from an other plane to the Dash. If I directly load the Dash there are no errors and the HDG digits doesn't work correctly until I import the MCPPRO.xml.

    I Steve is right, why this problem doesn't happen at the other planes profiles? Maybe because the Dash is very complex to be operated with the MCPPRO.
  • SlayerSlayer
    edited May 2016
    I have the pro version too so that's not an issue. I originally started the profile and have tested it on the non pro version too. The hash codes are the exact same between versions.

    if you get that error  don't bother trying to close every window that opens, just close GIT( ctrl alt del and close with task manager)

    The reason the big red X does not work is the same as before, the bespoke event you have selected must contain some code, if it's empty the red X is disabled, just pick a different event with something in it,  now the delete all will work again. if all your events are empty then just put anything in an empty event and now the delete all will work again. 

    I know at least 2 other people who are using this profile without these issues so this is as frustrating for me as it is you. 

    Another note for Steve too is that the heading display setup I used in the MJC used a decimal as well , the reason it is incrementing by 3.6  so that only confirms that somehow the decimals are getting removed in the bespoke events on import and in the settings of the profile too .

    I just tried what Martin said and now I get the error on my system too, if I start with a different aircraft and then switch to the majestic it deletes all my bespoke events.

    previously I had been starting the sim with the majestic right out the loading screen
    Steve McNitt
  • Martin1210Martin1210
    As Steve (Slayer) wrote, I've made a screenshot my Win10 Pro (German) Keyboard setting.
  • SlayerSlayer
    mysteriously if you shut down the sim and GIT then load the sim and majestic again the profile is working and the events aren't deleted. 

    It appears on the surface to be two separate problems or symptoms of the same problem?
    Steve McNitt
  • Martin1210Martin1210
    Yes, but I must load MJC directly. If I load any other plane and then MJC I get those errors. It's horrible to click "Ok" for each Bespoke event error.

    One thing I haven't tried is to disable my anti-virus, but then I would have this problem with the other profiles too...
  • SlayerSlayer
    edited May 2016

    Like I said , there are 2 issues at play here:

    1) Your system is removing the decimals when using my profile  ( I can't reproduce this problem)

    2)The profile doesn't seem to work anymore unless you load directly into the airplane first before anything else ( I can verify this problem on my system) 

    at first I thought when Martin was saying the heading that he meant the heading in the aircraft was increasing by 10 but it is really the heading display on the MCP and on that I also used a decimal, so now it makes perfect sense.. the default heading display does not work with the majestic, thats why I had to come up with using the knob position ( the formula for that is GS_HDG1_knob_ANGLE * 3.6)
    So if you remove the decimal and multiply the knob angle by 36 the heading display will increase by 10 instead of 1
    Steve McNitt
  • Martin1210Martin1210
    Yes Steve, I meant the heading on the MCP counts up by 10 and reaches values above 360 degrees. Sorry about this misunderstanding.

    If I start P3D and load the Dash and then start GIT my only problem is, that the MCPPRO digits for HDG and both Course are showing 360 and if I turn the MCPPRO CW the value at the MCPPRO displays goes up by 10 and down by 1. The values for ALT and the EFIS are working correctly.
  • Martin1210Martin1210
    If I import the MCPPRO.xml again, all digits at the MCPPRO are working correctly.
  • admin_ppsadmin_pps

    Hi Martin,

    I know this is a big ask; but could you try changing the Windows language to English. Clear out the Bespoke Events and config of the MCP PRO and try again.

    Thx

    Steve

  • admin_ppsadmin_pps

    Hey Steve,

    What do you mean by this:

    "2)The profile doesn't seem to work anymore unless you load directly into the airplane first before anything else ( I can verify this problem on my system)"

    Thx

    Steve

  • SlayerSlayer
    it means if I start the sim and the first aircraft I choose is the majestic, everything is fine.

    If I start with a default aircraft and then switch to the majestic I start getting errors like his screenshot above. All the events error and if you look in detective they are then blank.

    at this point you can't shutdown GIT because every event is causing an error and have to use task manager to shut it down. After a restart the events are back.

    I suppose if I closed every error box that came up then shutdown GIT it would save all blank events.
    Steve McNitt
  • admin_ppsadmin_pps

    That's weird. I'll look into it.

    Thx

    Steve

  • SlayerSlayer
    BTW that was with a clean profile, I deleted everything and only imported the majestic so I was working with a clean slate.

    In the meantime I updated the profile again for Martin to test, I've removed anything that used a decimal.  The heading is now read from a bespoke variable and updated in the start event  so it is much slower to update than the old method.
    Steve McNitt
  • admin_ppsadmin_pps

    Hey Steve,

    It looks like it was a language issue. I gave Martin a new version of GIT  that reinforced the language as English US when running the import/export code and he is reporting its working with your old profile. This should not have been necessary and more testing is to be done at his end, but so far it looks like a result!

    Best wishes

    Steve

  • SlayerSlayer
    Nice!
    Glad Martin is finally sorted.

    Were you able to reproduce the loading issue with loading the majestic after another aircraft or is it possibly something on my end?
    Steve McNitt
  • admin_ppsadmin_pps

    Hi Steve,

    Martin has confirmed today that everything is working OK, including your old profiles with the modified version I gave him. The issue of the Q400 being the start plane still exists so I will look at that over the next day or so and issue a new version.

    Best wishes

    Steve

Sign In or Register to comment.

© Vanilla Keystone Theme 2025