admin_pps
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.
admin_pps
Comments
-
Ok, what you are attempting to use is for X-Plane. In FSX/SE, you can use the Display Action DIVIDE_AS_DECIMAL_3_DECIMAL_PLACES but the only variables available are COM ACTIVE FREQUENCY:index and COM STANDBY FREQUENCY:index unless there are aircraft specific lvars that you can find. The variables above are being downloaded…
-
Its included in the latest GIT release from your account. You just need to configure the GIT GF166 tab as discussed in this thread. Best wishes Steve
-
I don't understand this: RB48 R D0 Heading bug at rot 1 (inc/dec RB48 R D1 Gyro drift + Kohlsman Can you explain it better. E.g. what events you are using, actions etc. You can also use Detective and enable event monitoring. When you use the controls in the VC, Detective will show what events it is using. Failing that…
-
GIT does detect DirectX joysticks, but the odd one needed to be hard coded. I guess the one you have will need this. I'm currently restoring my dev environment following a screw up by me restoring a failed raid disk. So give me a week or so and I will work with you to add support. Best wishes Steve
-
Use Windows Explorer to go into the GoFlight drivers directory, right click on Windows8Fixer.cmd and select Run As Administrator. If this does not fix the problem, remove ALL GoFlight hardware and repeat; then reconnect the GoFlight hardware. Repeat this process until it all works. Best wishes Steve
-
I don't think the SELECT events work with doors, I think they are for aircraft engines, throttles etc. Send the key press SHIFT+2 for the second door instead. Best wishes Steve
-
If the Bespoke Event simply has the Send task in it, then it looks like the aircraft is over-riding the event for some reason. You could try settings the ELECTRICAL MASTER BATTERY variable to 1 instead.
-
Have you checked its not configured in FSUIPC or GFConfig?
-
Yes you can edit the XML files - Settings.XML, PMDG.XML and SettingsXPlane.XML. You will see the GFT8 sections for each aircraft and then find <Device ID= entries and change the numbers to swap the device ID's. Take a backup first, just in case! Best wishes Steve
-
See my first response in this post: https://www.pollypotsoftware.org.uk/vanillaforums/discussion/1597/msfs-git-cannot-startup Best wishes Steve
-
Can you post your GIT log from the Log tab. Thx
-
You need a cockpit visible for the tabs to be enabled. Best wishes Steve
-
The last time I looked at this, I used the developer tools within MSFS and there is an option to drill down into the gauges and see the code (can't recall what the option is off hand). Looking at the code you can spot the events. Best wishes Steve
-
When copying the User Key please ensure that you are not using google translate or have a language selected on the website as this will change the User Key and make it invalid. Best wishes Steve
-
Yes, it could be a WASM event, but I don't know of a way to automatically find those as yet. Best wishes Steve
-
GFDevFSX is GoFlights software and has nothing to do with GIT. GoFlight's software never supported MSFS. Use GIT and where available use the FS Defaults button to configure the aircraft to behave like GoFlights software. Best wishes Steve
-
GIT mimics the dataref plugin when its not present. Currently there is no way of disabling this. I will need to work on it. Best wishes Steve
-
GoFlight only officially supported USB 1 and its what they always recommended if asked, however they supplied USB2 hubs when they supplied my airliner setup?! Some people have had no end of problems with USB 3, whilst others have had no problems at all. I'm guessing its down to firmware settings and the USB manufacturer.…
-
You need a suitable null zone when the throttle is idle because sometimes a joystick will not report 0 as its position and therefore the reversers will not engage because the 737 thinks its not fully idle. See this guide I wrote for FSUIPC and the 737 with the TQ6 to understand what I'm referring to:…
-
GIT makes no use of GFDevFSX - that is for GoFlights own driver software. Have you enabled and configured the MCP Pro and EFIS for the 787 in GIT? Best wishes Steve
-
Sometimes the developer of a gauge only monitors events to trigger changes and simply uses the variable to track current position etc. I would look for a suitable event. Best wishes Steve
-
You need to enable the devices in GIT on each tab, select the device no and make sure it says ENABLED next to it. Do the rotaries work on the MCP Pro, and its just the lights and displays not working? Best wishes Steve
-
The running away could be a couple things. Confirm its not a hardware fault by using GoFlights MCP Pro testing software: https://1drv.ms/u/s!AvmOqBMETlayh9ZQUzSikUTgvmwIyw?e=xGIgM8 This will show if your rotaries are jumping all over the place which will mean your rotary encoders need replacing. Secondly make sure you do…
-
Have you enabled and configured the devices or restored from backup your old config?
-
The documentation is out of date for getkvar as I have just checked the code and support is there for it. I suspect support for the PMDG is limited in both Lua and Detective because the SDK was doing all the work. I'll need to go over all the code to see what is happening. Best wishes Steve
-
Does the joystick work correctly before the autopilot is engaged?
-
If the 7X7X.... variables are genuine lvars then it could be they have just not been created by the aircraft at the point of testing. You can manually add them to the PMDG 737 aircraft section of the KnownLvars.xml file in Documents\GoFlight Interface Tool and see if they work correctly after restarting GIT. Any variables…
-
Create a new lua script so that you can query what the lvars are. E.g. print(getlvar("7X7X_Ground_Power_Light_Connected")) Remember to save the script and then you can run it in the Lua console and its current value will be show in the output area of the lua console. Best wishes Steve
-
Yes that is fine. Take a backup first in case you make any errors. GIT reads the aircraft name to determine the config to load. If you change the short name to be more specific for each version of the PMDG aircraft, you can get/build different configs for each variation that will load automatically. Best wishes Steve
-
Add this to global_aircraft.lua so it runs continuously (you may need to restart GIT after doing so):while (true) do if (getlvar("7X7X_Ground_Power_Light_Connected") == 0 and getlvar("7X7X_Power_Door") == 1) then setbvar("Bespoke Var 99", 1) else setbvar("Bespoke Var 99", 0) end …