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.
GIT and Streamdeck - my solution
If you are after more buttons to control your Sim Platform, cant buy another GoFLight module, you dont have Steve's "Virtual Flight Sim Hardware' product yet, and you happen to have a Stream Deck, then it IS possible to tie the Streamdeck buttons and GIT together.
GIT is really powerful for detecting and writing Bespoke events. Unfortunately it cant program/control Streamdeck buttons.
There are other hardware interface programs that can interact with Flight sims and Streamdeck (I own ALL of them) and yet none offer the same ease and flexibility with Sim interaction as GIT.
So this is how I tie GIT and Streamdeck together.
I use a free Streamdeck plugin called 'Pilot's Deck, a StreamDeck Plugin' (it works for MSFS, P3D and XPlane).
This plugin can read sim variable, set Streamdeck icons based on those values, but it does not have an event/scripting capability to code complex routines once you push a button. This is where GIT comes in handy.
The trick is to get the PD plugin to signal to GIT that you want a specific GIT bespoke event to be called.
I use something called Virtual Joystick (vJoy). and set it up for 1 axis and 120 buttons as my 'interface' between the PD plugin and GIT. GIT is able to see vJoy config as a joystick and can react to all of the 120 button 'presses' in vJoy.
The visual reaction and icons on the Streamdeck are configured with Pilot's Deck plugin.
For the 'action' operation in the plugin (do something in your Sim) I configure 'PD plugin to initiate a 'click' on one of the vJoy buttons.
In GIT, I write some Bespoke events, and then get GIT to call that bespoke event on receipt of a specific vJoy button.
So an example might be for landing lights on Streamdeck:
in the PilotsDeck plugin, create a button (you can tell it to change the button icon based on value of a particular lVar - it can do that relatively easily).
On the button press, configure the PD plugin to 'click' button 1 on vJoy interface 1.
In GIT create a toggle bespoke event (I use switch/case command in the bespoke event for powerful toggle control programming) to turn on or off LvArs and to call Simevents (or even call other GIT bespoke events you have created) to control your landing lights.
In GIT turn on joystick support, and configure it to react to vJoy's button 1, to call your bespoke toggle event to control landing lights.
The only catch Ive found is the joystick and button numbering in the PD plugin is a bit strange, so you will have to play around until you find the joystick ID and button ID in PD plugin and the corresponding interface and button number GIT knows this as.
GIT is really powerful for detecting and writing Bespoke events. Unfortunately it cant program/control Streamdeck buttons.
There are other hardware interface programs that can interact with Flight sims and Streamdeck (I own ALL of them) and yet none offer the same ease and flexibility with Sim interaction as GIT.
So this is how I tie GIT and Streamdeck together.
I use a free Streamdeck plugin called 'Pilot's Deck, a StreamDeck Plugin' (it works for MSFS, P3D and XPlane).
This plugin can read sim variable, set Streamdeck icons based on those values, but it does not have an event/scripting capability to code complex routines once you push a button. This is where GIT comes in handy.
The trick is to get the PD plugin to signal to GIT that you want a specific GIT bespoke event to be called.
I use something called Virtual Joystick (vJoy). and set it up for 1 axis and 120 buttons as my 'interface' between the PD plugin and GIT. GIT is able to see vJoy config as a joystick and can react to all of the 120 button 'presses' in vJoy.
The visual reaction and icons on the Streamdeck are configured with Pilot's Deck plugin.
For the 'action' operation in the plugin (do something in your Sim) I configure 'PD plugin to initiate a 'click' on one of the vJoy buttons.
In GIT, I write some Bespoke events, and then get GIT to call that bespoke event on receipt of a specific vJoy button.
So an example might be for landing lights on Streamdeck:
in the PilotsDeck plugin, create a button (you can tell it to change the button icon based on value of a particular lVar - it can do that relatively easily).
On the button press, configure the PD plugin to 'click' button 1 on vJoy interface 1.
In GIT create a toggle bespoke event (I use switch/case command in the bespoke event for powerful toggle control programming) to turn on or off LvArs and to call Simevents (or even call other GIT bespoke events you have created) to control your landing lights.
In GIT turn on joystick support, and configure it to react to vJoy's button 1, to call your bespoke toggle event to control landing lights.
The only catch Ive found is the joystick and button numbering in the PD plugin is a bit strange, so you will have to play around until you find the joystick ID and button ID in PD plugin and the corresponding interface and button number GIT knows this as.
Regards
David
David