1). Are these "undocumented FSX calls" methods/functions in one or more C++ classes? (i.e. .dll's)
There are many hundres of C or C++ undocumented function calls in FSX, the fun is trying to understand what they do without any source code or documentation.
In some cases, we even have to do direct memory access, which is not really news, we are doing like this since years, especially on FS9.
However, the general rule is, we first try to do it in the "official" way as much as possible, and use reverse-engineering derived features as sparsely as possible.
2). Can you use these methods to create custom Push backs for AI (no static ones); since you are eliminating them entire from the scenery when GSX is installed... ?
I guess we could, GSX by itself, doesn't really care if an airplane to be serviced is user controlled or AI. However, when servicing AI, even performance issues aside, it would open a new can of worms regarding the interaction between AIs and user airplane against AIs (eg. two push-backs could run into each other), which are simpler to deal with if we *know* it's only the user airplane that is going to be assisted.
So, the technology behind, doesn't have any limitation in principle, but we would like to release GSX this year, which means we'll focus on servicing the user airplane only, at least for the initial release. If the product will be well received, the obvious next evolution would be extending it to AIs as well.
3). Can you build addon packages for Military Marshallers/ground crew as well?
We could build anything, it's just a matter of market: if GSX will sell very well, it's just normal to expect all sort of expansions, like a Cargo package or a Military package.