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.
Key Press
Hi Steve
When I use the key press for a bespoke event in my a2a 172 they do not move the button in the VC. If I use the key board or the goflight config tool the buttons in the VC do move. I mention this because I am setting up the buttons on a gf 48 and most of them cause the correct action in the sim but some of them do not. I have tried different events on the same button and they work. I have triple checked the key sequence and have redone it a couple of times to be sure. I tried the key sequence on the keyboard and it worked as it should. I tried the same key sequence using the goflight config tool and it worked. That's when I noticed that the buttons in the virtual cockpit that the key sequence is mapped to are visibility moving with the keyboard and goflight tool but not in with git?
Thanks
Terry
When I use the key press for a bespoke event in my a2a 172 they do not move the button in the VC. If I use the key board or the goflight config tool the buttons in the VC do move. I mention this because I am setting up the buttons on a gf 48 and most of them cause the correct action in the sim but some of them do not. I have tried different events on the same button and they work. I have triple checked the key sequence and have redone it a couple of times to be sure. I tried the key sequence on the keyboard and it worked as it should. I tried the same key sequence using the goflight config tool and it worked. That's when I noticed that the buttons in the virtual cockpit that the key sequence is mapped to are visibility moving with the keyboard and goflight tool but not in with git?
Thanks
Terry
Comments
Hi Terry
Which key presses in particular? I have just done a quick test for LShift + 2 and it displayed the popup as expected. I couldn't find a key list for the 172 or a key configurator either?!
Make sure you don't have any other software intercepting key presses. Have you enabled the Goflight device? Does it work via the Test button in Detective?
Best wishes
Steve
I used the a2a configuration tool for the c172 to map the autopilot buttons. They are all control-shift-letter. If you have the 172, the configuration tool is in a tools folder in the p3d/a2a/ folder.
Yes the device is enabled and several of the buttons work. I forgot to use the test function but I will.
Thanks
Terry
I just used the test function and it did not work. The key sequence is control-shift-B mapped to the Baro button in a2a configurator.
Thanks
Terry
Hi Terry,
Confirmed bug. It works OK with FSX but not A2A. I'll see if I can make it compatible.
Best wishes
Steve
Thank you. If it makes any difference, I am using Prepar3d v2.5 with both hotfixes.
Terry
Afraid we went backwards with that one. The sendkey* did not work and all of the other key presses that were working quit.
Thanks
Terry
Check the date of InputSimulator.dll in your Goflight directory is today. If not uninstall, check its deleted and then reinstall.
Best wishes
Steve
Thanks
Terry
Ok Terry, looks like the installer hasn't picked up the new version. Just copy and paste this version into your Goflight directory:
https://www.dropbox.com/s/4vnujm0iw18eysi/InputSimulator.dll?dl=0
Thanks
Steve
The * version works for the Baro. You can also see the button move in the virtual cockpit. I tried the * key press on the alt and hdg buttons that had been working before and they also worked but interestingly the buttons in the VC did not move. It is strange that that one button is different?
I am curious. What is the difference between the key press and key press*?
Thanks for making it work.
Terry
It took me a day to work this out.
SendKey* reverses the button down event and pauses between button up and down. I have to admit its very odd. I tried all the various recommendation regarding supporting DirectX and key presses but nothing would work with the A2A. I eventually stumbled on the need for a pause and then worked backwards from there, realising it wanted button up flags before button down. Makes no logical sense, but it does appear to work.
I would always use SendKey unless it doesn't work and then try SendKey*.
Thanks for testing.
Best wishes
Steve
Thank you for taking the time to fix.
Terry