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 64bit and GIT 3.4.1.0 - Errors

Hi,

V3.4.1.0 of GIT doesnt seem to be compatible with the latest 64bit version of the Majestic Q400.
I keep getting
"Event MJC_*" errors thrown by GIT.

Has anyone been able to get their version of GIT to work with the 64 bit Q400?

Regards
David
Regards
David

Comments

  • I also have a crash every time I try to use the tool with Majestic in p3dv4.1, in my mcp I can adjust the ALT but for some reason when try to adjust the HDG the sim always crashed
  • edited October 2017
    Guys the new version of the Q400 only operates with some new interfaces: XML, UDP, Joystick connector and RPC. It is different than the previous two version so please give Polypot Steve some time to sort it out. Not sure my profile will ever be able to work with this aircraft until there is a new method to do so. Even then it will require a rewrite. On the surface it looks easier , but currently as far as I can see the normal methods of interfacing to an aircraft will not work. Only the variables that have hardcoded P3D LVARS/Simconnect pre-programed would work and my profile used a mix of both...

    Now you know why they charged 20 bucks. It was a complete rewrite of the code, but it was necessary for the upcoming training version :/

    Edit: XML was the original interface which was used to connect to the aircraft but still references 32 bit!? Not sure if it's just a matter of recalculating the intvars or if the variables themselves have changed so the old ones are invalid. Regardless it will take me some time to go through
    Steve McNitt
  • Slayer/Steve, we understand all the effort and good job u both did and still doing,, this an amazing tool and and sorry if we are anxious to have it available for this great plane once again. keep the good job. THANK YOUN
  • I have an idea to get around using XML with mouse events but just got my hardware up and running again so haven't had a chance to test it yet. It would require a complete rewrite to get rid of all the XML stuff but it may be a way forward.
    Steve McNitt
  • Great news, Steve!
  • I'll try to get something out for you guys soon at least with basic functionality. The mouse events are working OK in my tests the only drawback is button lights are going to be non functional and I'll probably not redo the radios.

    Some really smart people have used FSUIPC to control their Goflight since the Dash also has IPC interface but I have zero knowledge on that method and it looks very complex(and is beyond the scope of this forum)
    Steve McNitt
  • I have some good news and bad news to report. Using the newer pseudo LVARs works ( at least what I have tested so far). That means the button lights etc can work.

    The bad news is that I have to completely remove all traces of the original method use to interface to the aircraft. Basically I have to start from scratch to prevent any crashes but I have made some good progress so far and going from memory some items will not work properly because GIT cannot handle WORDs(I think).
    Steve McNitt
  • Very good news, thx for ur effort,, we (I) really appreciate
  • yes, thank you for all your efforts
  • give this a try , for now it is the MCPPro only but there are bespokes in there for overhead panel.

    Steve McNitt
  • Hi, I tried this out and all the commands seem to work great. I only have the regular MCP btw. Some of the default FS AP settings seem to work (i.e. altitude display/rotary knob). I didn't see an AP Cancel command, so I mapped the disengage bar on my mcp to the AP standby. Is there any way to get the blinking a/p diseng light to turn off?

    Based on your work thus far, Do you think it will eventually be possible to create commands for every thing? i.e. turn on the APU (In the previous version, I was able to create a command that would turn on the APU Pwr, Start, and Gen all with one button. I was able to do it with that spreadsheet that had all the mjc var read and write codes on it.

    Thanks again for your help

    Bill

    Thanks
  • Yes It will be possible.

    This new profile is using a few different methods to send button presses etc. 1) Simconnect vars provided by majestic ( there are new ones) 2) Fake LVARs provided by GIT 3) Mouse events hooked into by GIT

    The stby button is in the profile I just hadn't assigned it to anything

    I've added the APU stuff you mentioned in detective , it should be really easy to string them together with another bespoke event with the appropriate wait times added in between button presses. I believe you will have to use the " call" function. I could try to create an auto start sequence if you'd like that could be one button press.

    Don't try to use any codes or the profile will crash.

    Going to start a new thread for beta and try to regularly add more and more stuff as requested. If you see anything you want that's not available in the detective let me know.
    Steve McNitt
  • awesome...Yeah, my 32 bit q400 apu was just a bunch of individual commands called up with sleep commands to get it all to work. I also had one t8 switch that would fire up one engine. Basically, it would move the eng 1 knob from off to norm, then it would push the start button. I'd then do another toggle switch for eng 2.

    so, is there no easy way for others to create new commands via detective like we could before using the read and write vars via that program that would tell you what to enter? I forgot the name of the tool. I ask because I'd rather not have to continue bothering you to add new commands as I'm sure there are better things you could be doing with your time.

    Regards
    Bill
  • You can use any of the 3 methods posted above, just not the read/write codes
    Steve McNitt
  • question, as an example, how did you go about determining that 1MJC AP Button works by the following: Send 43 with 536870912(CptPanel_guage:mjc84_main.dll)? I see a list of those cptpanel_guage under mse clicks, but have no idea which is which

    How would I figure that out? I admit I'm a total noob at this. I can use detective to run the LVARS, and I see the list of SC Vars, but have no idea where the number 43 and the 536870912 come from.

    thanks
  • also, where do I find the Majestic sim connect variables?

  • edited November 2017
    ok, never mind about my first question, I see when I create a mouse event, it automatically brings in those numbers. However, is it just trial and error trying to figure out which cptpanel gauge is what?

    Is there a detective if you will for mouse clks?
  • I've been making a spreadsheet over time. Got a bunch of them mapped out.

    https://docs.google.com/spreadsheets/d/1NkIK2UxriR2WW7dwKtebS4ZweQRkmo60laqJALITaHk/edit?usp=drivesdk

    The other variables show up in the detective on the first tab at the top. They are mixed in with the default stuff so its hard to tell but after working with git so long they aren't hard to spot
    Steve McNitt
  • thanks, I'll look at it. for the life of me, I can't seem to turn off the APU with a t8 switch. I created a command that calls the apu power, start, and gen from you and it will turn on, but I can't seem to get it to turn off. I can get it to turn off in detective if I use a right click command, however it doesn't work when I flip the t8 toggle. I don't suppose you know why it's not working?

    Thanks
  • edited November 2017
    Copy that bepoke event , rename to apu off or whatever and then edit it to a right click instead of a left. Then assign that to your off position for your switch.
    Steve McNitt
  • Some buttons and switches require a left and right click, some just a left click will cycle the switch. Depends on how the programmer set it up
    Steve McNitt
  • actually, the buttons work with a left mouse click as well, but It's randomly working for me. In fact I'm getting lock ups and crashes on my end, especially if I try to edit a mouse click event. Is it possible for you to create a bespoke event that turns on the apu, and then another that turns everything off? I just want to see what I'm doing wrong.

    Thanks
Sign In or Register to comment.