Developer's Backdoor > GSX Backdoor
We would like to hear your suggestions about a GSX Open API
ab-tools:
Hello Umberto,
Daniel pointed me to this thread - I'm the main developer behind the FS-FlightControl Instructor Station.
And yes, we would be VERY interested to directly integrate with GSX where basically two things would be important:
1. Ability to control the GSX ground services remotely via network based API (TCP, UDP or even via SimConnect client events).
2. GSX menu not shown in Prepar3D/FSX when GSX is controlled remotely.
There was a longer thread about our product and potential GSX integration already here in your forum in this thread:
http://www.fsdreamteam.com/forum/index.php?topic=14025.0
It would be really great if you could open some sort of API to remote control your GSX product!
Please let me know if you should need any further information.
You can also contact me directly at info@fs-flightcontrol.com.
Best regards from Germany
Andreas
virtuali:
--- Quote from: ab-tools on January 03, 2018, 05:35:47 pm ---And yes, we would be VERY interested to directly integrate with GSX where basically two things would be important:
1. Ability to control the GSX ground services remotely via network based API (TCP, UDP or even via SimConnect client events).
2. GSX menu not shown in Prepar3D/FSX when GSX is controlled remotely.
--- End quote ---
I'll surely contact you but, I must anticipate this wouldn't be the easiest thing to add, which requires far more work than what was discussed in this thread, which were basically just adding more published L: variables that developers could read (several of them are already there).
ab-tools:
Hello Umberto,
first thanks a lot for your quick reply!
As FS-FlightControl is an external program we can't easily access "LVars", but as far as I understood you also just use SimConnect directly (and not FSUIPC) the same as we do.
If that's the case I would suggest to simply make the variables that you currently "offer" as "LVars" also available as "client data" via SimConnect.
As you are familiar with SimConnect obviously using the "client data" feature should be very easy to do. That's the SimConnect functions you would need:
http://www.prepar3d.com/SDKv4/sdk/simconnect_api/references/general_functions.html#SimConnect_AddToClientDataDefinition
http://www.prepar3d.com/SDKv4/sdk/simconnect_api/references/general_functions.html#SimConnect_RequestClientData
http://www.prepar3d.com/SDKv4/sdk/simconnect_api/references/general_functions.html#SimConnect_SetClientData
Additionally we could use "client events" to trigger certain actions:
http://www.prepar3d.com/SDKv4/sdk/simconnect_api/references/general_functions.html#SimConnect_TransmitClientEvent
This way everything would be done directly within SimConnect and no additional interface (like TCP or UDP) would need to be implemented.
Please don't hesitate to let me know if you should have any further question - really looking forward to work together with you to make this happen!
Best regards
Andreas
virtuali:
--- Quote from: ab-tools on January 04, 2018, 10:38:04 am ---As FS-FlightControl is an external program we can't easily access "LVars"
--- End quote ---
Understood (GSX can access L: vars even if it's an external program, because it connects with the Addon Manager, which is a .DLL): we used L: vars because they are very easy to use from XML gauges and they can be used by LINDA, for example.
--- Quote ---but as far as I understood you also just use SimConnect directly (and not FSUIPC) the same as we do.
--- End quote ---
Yes.
--- Quote ---If that's the case I would suggest to simply make the variables that you currently "offer" as "LVars" also available as "client data" via SimConnect. As you are familiar with SimConnect obviously using the "client data" feature should be very easy to do. That's the SimConnect functions you would need:
--- End quote ---
We are are obviously aware of the Simconnect client data, which is how GSX communicates with SODE...
--- Quote ---Please don't hesitate to let me know if you should have any further question - really looking forward to work together with you to make this happen!
--- End quote ---
The issue is not how to communicate data between two programs: that's the easiest way and it's just a minor detail. The REAL issue is making GSX aware of it MIGHT be remotely controlled, without affecting its normal usage and THIS is what is really tricky.
ab-tools:
Hello Umberto,
--- Quote ---The issue is not how to communicate data between two programs: that's the easiest way and it's just a minor detail. The REAL issue is making GSX aware of it MIGHT be remotely controlled, without affecting its normal usage and THIS is what is really tricky.
--- End quote ---
Sure, this would need to be done, but I think it would be worth the effort:
We really get a lot of requests by customers to "remote control" GSX or AES and I don't want to work with AES as long as there is no Prepar3D version available by Aerosoft (which I don't expect any soon). So I really would like to work with you to get GSX integrated with FS-FlightControl.
And also apart from remote controlling GSX with FS-FlightControl, I'm sure there would be many other usage scenarios for that:
Especially customers that do have a full cockpit really do not like the menu options to be shown inside the main Prepar3D/FSX window as it kind of "destroys the illusion". Therefore, having an option to remote control GSX without a menu being shown in Prepar3D/FSX being it using FS-FlightControl or a different tool would definitely be a great option for many users!
I am a developer myself, so I obviously know that there are always side-effects and things are not so easy as they sound in the first place, but I could think of this as a "kind of simple" solution:
- We could transmit a SimConnect client event to enable remote controlling.
- After GSX has received this client event it no longer shows the GSX menu in Prepar3D/FSX, but instead provides exactly the same menu options using a SimConnect client variable.
- FS-FlightControl (or any other tool) could then trigger exactly the same actions (again using a SimConnect client event) as the user "normally" can by selecting the appropriate menu option in Prepar3D/FSX itself.
That way - as it's just a new interface to exactly the same options - I would expect/hope that not a lot needs to be changed inside GSX to make it work also remotely controlled.
Please let me know your thoughts about that.
As mentioned I'm happy to discuss that also via e-mail (info@fs-flightcontrol.com) directly if you prefer that.
Best regards and thanks again for getting back to me so quickly
Andreas
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version