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.
Add programmable virtual GF devices?
Hi Steve,
I often find myself not physically being at my home PC where my GF device are connected to my main FS PC. However, whenever I have down time (travel, etc.), I'd like to be able to program my devices for an aircraft on another PC or laptop where I have P3D installed (and the aircraft) but do NOT have all my GF devices connected.
So, I was thinking if it would be possible to define "virtual" GF devices that could be added and appear in the GF UI's tabs ... maybe use a different color to indicate it's a "virtual" GF-166 or T8, P8, etc.
With this in place, we can then continue to detect/define/code the Bespokes/Lvars etc. for whatever aircraft we're setting up in P3D or XP11 anywhere at anytime (lunch break, vacation, work travel, etc.). The virtual GF device would visually emulate the same controls/switches/buttons and interact with P3D/XP11.
The configuration/setting of the Virtual GF devices could be exported once one is back at their actual main FS PC with the physical GF devices connected. One can then Import the virtual device and bespokes/lvars etc. into the main FS PC.
You already have the "test" button, so essentially use that code/logic and expand it to a virtual GF device. To extend this idea even further, allow these "virtual" GF devices to have their own floating windows that could be displayed on a Multi "touch" monitor setup. And pushing that idea out even more, the virtual GF devices could be customize visually to look like their real world parts (2D only). And finally allow these Virtual devices to operate on networked PCs communicating with a GIT "server" on the main FS PC that does the actually interaction with the aircraft (possibly expand to iOS and/or Android apps using iPads/tablets similar to VAInterface folks with their CDUs).
I know this going to be lots of work, but I'd happily pay for a GIT "extension" add-on or upgrade cost that provides this functionality. It would certainly need to be done in phases or get some additional programming resources on-board, but I think it would have considerable potential beyond GF modules but without "excluding" GF modules since there would be an "Import" option.
What do you think?
Cheers, Rob.
I often find myself not physically being at my home PC where my GF device are connected to my main FS PC. However, whenever I have down time (travel, etc.), I'd like to be able to program my devices for an aircraft on another PC or laptop where I have P3D installed (and the aircraft) but do NOT have all my GF devices connected.
So, I was thinking if it would be possible to define "virtual" GF devices that could be added and appear in the GF UI's tabs ... maybe use a different color to indicate it's a "virtual" GF-166 or T8, P8, etc.
With this in place, we can then continue to detect/define/code the Bespokes/Lvars etc. for whatever aircraft we're setting up in P3D or XP11 anywhere at anytime (lunch break, vacation, work travel, etc.). The virtual GF device would visually emulate the same controls/switches/buttons and interact with P3D/XP11.
The configuration/setting of the Virtual GF devices could be exported once one is back at their actual main FS PC with the physical GF devices connected. One can then Import the virtual device and bespokes/lvars etc. into the main FS PC.
You already have the "test" button, so essentially use that code/logic and expand it to a virtual GF device. To extend this idea even further, allow these "virtual" GF devices to have their own floating windows that could be displayed on a Multi "touch" monitor setup. And pushing that idea out even more, the virtual GF devices could be customize visually to look like their real world parts (2D only). And finally allow these Virtual devices to operate on networked PCs communicating with a GIT "server" on the main FS PC that does the actually interaction with the aircraft (possibly expand to iOS and/or Android apps using iPads/tablets similar to VAInterface folks with their CDUs).
I know this going to be lots of work, but I'd happily pay for a GIT "extension" add-on or upgrade cost that provides this functionality. It would certainly need to be done in phases or get some additional programming resources on-board, but I think it would have considerable potential beyond GF modules but without "excluding" GF modules since there would be an "Import" option.
What do you think?
Cheers, Rob.
Comments
The first part is very easy. I have done it in the past by tweaking the Qty property of a particular GoFlight object class, so I know all the code works fine with fake GF devices. I will add this to the development plan.
The second part I need to have a think about.
Best wishes
Steve
Cheers, Rob.
Best wishes
Steve
Cheers, Rob.