Slayer
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.
Slayer
Comments
-
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…
-
You can use any of the 3 methods posted above, just not the read/write codes
-
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…
-
give this a try , for now it is the MCPPro only but there are bespokes in there for overhead panel.
-
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…
-
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…
-
This is a very rough release NOT complete , lots of stuff is not implemented , if you don't want to test it and offer feedback/suggestions please wait until the final version. Only proof of concept at this point using commands that Mokney used for examples. Please see installation.txt on how to install as it is not a…
-
Ok this profile will take me a bit longer to complete as it looks like there are no native datarefs to access in this aircraft. I found a plugin that will hopefully allow me to hook into it though and then out to GIT/GF stuff. Basically have to build 2 profiles to make it work 1 for the plugin and 1 for GIT. I'll post a…
-
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.
-
Working now , thanks for fast response A+ support.
-
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…
-
I'll look at it again as well when there is a way to make it work. I have a suspicion that the next version(training) will make things very easy because there will be lots of 2d panels and they are easier to hook into vs the old method, but that may be a ways off yet.
-
I put out an updated profile please see the new post in the user provided BE forum.
-
Most likely an incomplete import. I would suggest if you have other profiles to make sure they are exported/ backed up then try removing your goflight folder in documents and trying again with a fresh import. It has been working with all patches and pro version up until this point. the _MC on the end is my shorthand for…
-
Try a different dataref. Get Dataref tool then you can accurately see which event or events are firing when you flip the switch. DRT shows how long ago the dataref was used DRE does not. Many times you will find one event or command fires several others, you have to figure out which is the proper one that will make the…
-
In the detective. Make sure you have monitor DRE private datarefs set as well. You have to build BE's for them.
-
Thanks for sharing your findings
-
You can rename the bespoke variables, it just moves it to the bottom of the list when you do. Makes it much easier to work with.
-
The 747 has built in support , so you need the newest drivers from Goflights website and the newest version of GIT downloaded from your account page. The Q400 is a profile you can dl from the main page, then use the wizard to import the profile.
-
Have you tried excluding the Goflight directory from your virus scanner or windows defender? Also could be a messed up .NET framework or visual studio not installed properly, Have you run windows update to make sure those are up to date? Have you tried starting GIT after you start the sim and load the aircraft? How are you…
-
edit that was with the C172, didnt try other aircraft
-
Try sim/cockpit2/engine/actuators/ignition_key [0](1 through 4 are the different key position values, if you send it 4 (start position) it should work) I tried it and it works and will hold the key in the start position you just have to send it a 3 to return to the spring loaded position on button or switch release
-
Hi Bill. I've done a ton more of the overhead buttons /dials/switches if you want my updated bespoke events you can then assign them as you want. All the dimmers etc are near the bottom as they are the newest BE"s. I've been working on and off with another user here to get his RP48's programmed but I don't own the hardware…
-
Hi Bill. I've done a ton more of the overhead buttons /dials/switches if you want my updated bespoke events you can then assign them as you want. All the dimmers etc are near the bottom as they are the newest BE"s. I've been working on and off with another user here to get his RP48's programmed but I don't own the hardware…
-
The Q400 radios work like that. You could try loading default Gf166 radio profiles but If I recall right they don't work with the Q400, thats why I programmed them the way they work in the real thing
-
Hey Martin, the easiest way to find datarefs and see what they do is to use a plugin called "dataref tool". While it is not recommended to use GIT and this together I use it to find the datarefs and see what values change when a switch or knob or whatever is used. It is very handy as you can search datarefs by name so if…
-
Sorry for the late reply, yes I meant to say mouse clicks here is a list of mouse clicks I have compiled so far: https://docs.google.com/spreadsheets/d/1NkIK2UxriR2WW7dwKtebS4ZweQRkmo60laqJALITaHk/edit?usp=sharing
-
I've gotten the knobs to work using mouse events. Some of the stuff in the majestic list just flat out doesn't work or more info is needed to make it work. I'm working on an update with more bespoke events but it is a tedious process.
-
The Any-Aircraft.xml was made with XP10 in mind so should work with default planes from 10 . From what I'm seeing most of the new defaults in 11 are essentially payware planes with custom datarefs.
-
The new default aircraft in XP 11 have their own datatarefs , so some stock datarefs may partially work but you have to dig in and find the right ones because the stock ones are only part of the equation.