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.
Solution for import problems
Hi Steve,
When importing bespokes via Detective this is very problematic due to the ID value as they could duplicate other existing bespoke ID values. To solve this problem, I was wondering if you would consider moving to a GUID for the ID value. This would almost certainly ensure no replication and should work across any PC/file. It would also ensure any /type="Call" events would still work as expected since they would point to the GUID.
Example:
Set ID="106" to be ID="7ae3a56d-ae20-4d43-9ed8-24c928460b34"
What do you think?
Cheers, Rob.
When importing bespokes via Detective this is very problematic due to the ID value as they could duplicate other existing bespoke ID values. To solve this problem, I was wondering if you would consider moving to a GUID for the ID value. This would almost certainly ensure no replication and should work across any PC/file. It would also ensure any /type="Call" events would still work as expected since they would point to the GUID.
Example:
</code><Event Name="_MV_WX_RANGE_DEC" ID="106" Backgnd="False">
<Task ID="2" Type="If" Var="WX_Radar_Range" Operator="GREATER_THAN" Value="0" />
<Task ID="4" Type="Call" BespokeID="104" />
</Event><code class="CodeInline">Set ID="106" to be ID="7ae3a56d-ae20-4d43-9ed8-24c928460b34"
What do you think?
Cheers, Rob.
Comments
Thx
Steve
If I attempt to "Import" Bespokes from within Detective it will work without "error". However, if the bespoke file I'm importing has ID's the same as any existing ID's in my current working bespokes they will conflict when I come to assign them to a module (P8, T8, etc.).
So what I've been doing is manually renumbering the ID's to ensure they are unique and also making sure the "Call" BespokeID's are modified to correctly point to the updated IDs.
Why am I doing this you ask ... I have the Milviz/REX WX radar installed in several aircraft and it uses the same events/Lvars. So when I attempt to import the WX from an existing aircraft (into my different aircraft) the import will fail (more accurately, partially works) ... this is because the ID's are already in use for my existing aircraft.
To work around this, I've created a separate Bespoke file and module file just for MV/REX WX radar setup. However, there is still no guarantee that the ID's will be unique and could conflict as I progress with building more and more aircraft.
I would be able to avoid this work if the IDs where GUIDs as it would ensure uniqueness (with 99.9% certainty) and I'd never have to worry about ID conflicts. Similar in concept as to why Microsoft used GUIDs for their object identification knowing that an SDK could generate more objects and they needed to ensure uniqueness for references across content providers.
Cheers, Rob.
By the way, made some progress on the virtual modules for tablets project. Got a prototype running across all platforms to prove concept, so all systems go!
Don't suppose you'll be in Las Vegas June 8-11 for FSExpo? Would love to chat.
Cheers, Rob.
Just a quick update on the project you proposed.
The client software is complete (Alpha) and works with test data on UWP/Windows, Android and IOS. It supports buttons, switches, rotaries, selectors, LED's, LED displays and smart text so buttons can have text that lights up etc. All the gestures are in place also along with the async comms. It also supports multiple virtual panels (made up of modules) that can be swiped in or out.
I'm about 40% done on the Virtual Hardware Builder that allows pre built modules to be slotted into a virtual panel. The Pro version of this will allow a user to build completely custom components (switches, rotaries etc) and add them to a custom module/panel for ultimate flexibility.
The last part is the GIT update and the standalone server product for non GIT users.
Its looking good for beta testing and delivery before Xmas.
I will let you know when its ready to Beta test.
Thanks for the idea; the more I work on it, the more I think flight simmers are going to love this product suite.
Best wishes
Steve
Did you include in your plan the ability to "page" a single device ... meaning users could create pages that are control sets ... i.e. Page 1 would be all Autopilot related controls, Page 2 might be all aircraft lighting controls, Page 3 PACKs and bleeds, etc. etc. basically allowing a user to have just 2 or 3 devices that could be used to control everything. Users would just swipe left or right to move from page to page on a single device.
Have you also thought about selling "Pre-configured" aircraft sets? Some of these aircraft can take considerable time and effort to get all their respective controls mapped out (I know on the more complex aircraft I've put in well over 60 hrs and that's just one aircraft).
Looking forward to xmas!!
Cheers, Rob.
Have you also thought about selling "Pre-configured" aircraft sets? … " - I have been thinking about doing this for GIT for a while now and for this new product. I think for the PMDG aircraft it would be cost effective and I could sell it for a low price. Other aircraft, it may be just be too expensive for end users as they complain about the cost of GIT already; let alone paying for configs. I do find this bizarre though as they pay hundreds, if not thousands of dollars for the GoFlight hardware and then rage about a few dollars for software to run it all as if that has no value, even though the development time has been massive, let alone the support and maintenance costs
Best wishes
Steve
Cheers, Rob.
Just an update on the Virtual Hardware project. Today I hit a key milestone and completed the first successful end to end test using a virtual rotary on a tablet which successfully controlled the Heading bug in FSX!
Best wishes
Steve
Just another update on the Virtual Hardware project. Another milestone just reached. I built a test Com radio in the virtual hardware builder and have the COM events working on rotaries and the LCD displays displaying actual COM data from the sim!
Best wishes
Steve