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.
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
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
David
Comments
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
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)
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).
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
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.
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
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
Is there a detective if you will for mouse clks?
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
Thanks
Thanks