Developer's Backdoor > GSX Backdoor

GSX SDK

<< < (2/2)

virtuali:

--- Quote from: BenBaron on August 19, 2017, 05:37:06 pm ---EDIT: I noticed, you are providing some LVars in the manual...as far as I can remember those are only accessible from inside the FS process, so by gauge or dll. So my question still holds for external interfacing and a more refined API 
--- End quote ---

Those variables are the only way available to interface with GSX. What are you trying to achieve, exactly ? LVar surely can be accessed by out-of process modules, perhaps using FSUIPC+LUA, or may using Linda:

https://www.avsim.com/forums/topic/500848-explanation-of-lindas-gsx-door-service/

That's just an example, which has been made in a way more complex than it might have been, since the original poster commented about GSX not supplying variables to indicate when a service starts/stops, which as you already noticed, is no longer the case.

BenBaron:
Thanks Umberto for the fast reply.

I am looking into ways to automate the gsx processes programmatically for a small project of mine, thus it would also be nice if one could trigger those easily instead of simply reading their status. I know I can fetch the data into my external program (since there are other things I want to interface with inside the fs process I might write a small gauge in C++ anyways and simply add some functionality to parse the gsx data to my external program).

But if you were like: "You know, GSX version 2 is right around the corner with a super efficient and flexible API included, so better wait for that." ;), I would reconsider my whole design and try without running something extra inside the fs process.  :D

Nevertheless, thanks for all your efforts for the community.

All the best, Benny

virtuali:

--- Quote from: BenBaron on August 22, 2017, 11:20:13 am --- it would also be nice if one could trigger those easily instead of simply reading their status.
--- End quote ---

Everything in GSX is made using standard Simconnect calls so, you could control it remotely (either from another app or another PC), by firing the event to display its menu, and then send the standard Simconnects events to select menu choices.

Sure, it will show the menu for a brief time so, it won't be as seamless as a proper remote API but, it might be easier to code, it won't require any changes in GSX from our side, and it might not be very difficult to keep updated, in case we would add new features to GSX.

Navigation

[0] Message Index

[*] Previous page