FSDreamTeam forum
Developer's Backdoor => GSX Backdoor => Topic started by: virtuali on November 16, 2012, 05:37:29 pm
-
As you probably know, GSX has been a very good product for us, it's by large our fastest selling product, and has constantly grown following users suggestions, and it's a way better product today than it was 9 months ago when it was released. With GSX, users are discovering way more airports than ever, since it gives life and purpose even to default airports. And, since it's 100% and officially compatible with Prepar3D, is open to the future. It's our main product, so we are not letting it going anywhere, but will keep improving it.
There are so many different uses for it and every user need is different and many 3rd party developers privately contacted me in the past to discuss some way to interface their application with GSX. Some even did it without our help, with smart reverse-engineering, but it's clear everything would work better if we openly supported an official way to interface with it.
Some example of possible applications that interface with GSX that have been suggested are:
- Controlling GSX using voice command
- Having a Virtual Co-pilot function that will operate GSX on his own
- Operating GSX from a networked PC
- Putting GSX messages on a different screen, perhaps even a different device like a phone or a tablet.
- Using GSX when sharing a cockpit when flying online
These are just examples, but I'm sure other developers might add their own ideas. There's a whole area of possible interactions for sceneries, for example. Our own sceneries use some GSX-exclusive features, maybe other scenery developers would like to use it too, this will increase the value of the scenery to GSX users, and there are many of them...
We had some discussions about how an API might work, but we would like to hear your ideas about it so, we opened a Developers area on this forum.
If you do add-ons for FSX and would like to give your feedback about what you would need to interface with GSX with your application, JOIN that area on our forum this way:
1) If you are already registered on our forum, just send me a PM (Private Message), so I can enable your user account to access that area.
OR
2) If you haven't registered to this forum yet, just do it now, and send me a short message o the forum introducing yourself, so your new account can be enabled to the Developers area.
-
Hello FSDT,
It would be nice if you could make a ground service crew type of game, where my job would be to service the AI traffic in fsx.
Or a Cargo loading crew :)
I want to be the guy doing the push backs!!!
-
I'm sorry but, maybe my message wasn't worded clearly enough: this is NOT a post asking to suggestions for new GSX FEATURES, there are many other discussions for that.
This post is meant as a request for 3rd party developers to give their feedback about what they would like to have, as a Programming Interface, to connect THEIR OWN products to GSX. We would like to know what their needs are to make it easy for them to interface their own products with GSX. There are other places to discuss what might be added to GSX or future versions of it.
-
I'm sorry but, maybe my message wasn't worded clearly enough
Was certainly clear enough to me, Umberto. Hopefully, lots of developers will take advantage of the opportunity.
-
Custom pushback tool thing. Like what you guys do with your airports eg KLAX. From this parking to this node.
-
- Operating GSX from a networked PC
- Putting GSX messages on a different screen, perhaps even a different device like a phone or a tablet.
Yes, yes -- this is the area I am very interested in.
With your permission, of course, I'd like to be able to map any support you provide, such as via the SimConnect ClientData system, to FSUIPC controls and/or offsets so that folks have a choice, and can maybe do interesting things via WideFS and/or Lua plug-ins themslves. But my particular initial implementation would be to get the messages and menus and their responses off the FSX screen and onto a client PC, probably on a touch screen on the wall of my cockpit!" ;-)
If you do add-ons for FSX and would like to give your feedback about what you would need to interface with GSX with your application, JOIN that area on our forum this way:
1) If you are already registered on our forum, just send me a PM (Private Message), so I can enable your user account to access that area.
I'm not sure I want to contribute towards your design, as I'm sure you will come up with something better than I could think of -- providing it allows at least the above to be accomplished, and hopefully also the other things you list too, then I'll be happy to implement to it.
Best Regards
Pete
-
Yes, yes -- this is the area I am very interested in.
Hello Pete, I've enabled your account to the developers area, we'll continue there.
-
Dear Umberto,
I'm not a third-party developer, but I've one of those Saitek X-52 Pro HOTAS systems. Several years ago, someone made a program that allowed FS9 to interface with all of Saitek's HOTAS systems with screens, like the X-52, X-52 Pro, and X-65. Since I finally rid myself of FS9 because I bought an FSX capable Win-7 (x64) desktop, I don't have as many options with my X-52Pro as I once did.
It would be really cool (I don't know much about programming in that fashion) if the Saitek controllers and joysticks with screens could interface with GSX and/or your airports.
I love that GSX is so end-user malleable. I don't know many developers who would take the time to listen to end-users as you do.
Thank you very much for what has turned out to be my FAVORITE add-on for any flight simulator.
Gratefully requested,
Clinton
-
It would be really cool (I don't know much about programming in that fashion) if the Saitek controllers and joysticks with screens could interface with GSX and/or your airports.
That should be fairly easy to do: just use the Saitek SST program, and assign the GSX hotkey to one button, and the number keys (which will be valid with any FSX transparent menu, not just GSX) to other buttons.
-
Virtuali,
Is this opened to strictly 3rd Party payware developers only or can seriously "customer/developers" be included in this?
If, so, I'm very interested in the following BOLD highlighted areas (along with what Mr. Dowson might be up to) and the inclusion of API calls for use with speech-to-text products like SpeechBuddy. Awaiting a response & will send you a PM shortly.
As you probably know, ...every user need is different and many 3rd party developers privately contacted me in the past to discuss some way to interface their application with GSX.
...Some example of possible applications that interface with GSX that have been suggested are:
- Controlling GSX using voice command
- Having a Virtual Co-pilot function that will operate GSX on his own
- Operating GSX from a networked PC
- Putting GSX messages on a different screen, perhaps even a different device like a phone or a tablet.
- Using GSX when sharing a cockpit when flying online
These are just examples, but I'm sure other developers might add their own ideas. There's a whole area of possible interactions for sceneries, for example. Our own sceneries use some GSX-exclusive features, maybe other scenery developers would like to use it too, this will increase the value of the scenery to GSX users, and there are many of them...
We had some discussions about how an API might work, but we would like to hear your ideas about it so, we opened a Developers area on this forum.
If you do add-ons for FSX and would like to give your feedback about what you would need to interface with GSX with your application, JOIN that area on our forum this way:
1) If you are already registered on our forum, just send me a PM (Private Message), so I can enable your user account to access that area....
-
Is this opened to strictly 3rd Party payware developers only or can seriously "customer/developers" be included in this?
It's open to any developer, regardless if it's for payware or freeware, provided he's able to code add-ons.
If you agree with my points, so you quoted in bold, that's fine, of course I know those would be useful to have.
But it's best this thread would be opened to developers only, otherwise this would start becoming a "features request" thread, which is not what we want to do here.
-
Is this opened to strictly 3rd Party payware developers only or can seriously "customer/developers" be included in this?
It's open to any developer, regardless if it's for payware or freeware, provided he's able to code add-ons.
If you agree with my points, so you quoted in bold, that's fine, of course I know those would be useful to have.
But it's best this thread would be opened to developers only, otherwise this would start becoming a "features request" thread, which is not what we want to do here.
Couldn't agree more with you here; I'll send you a PM with some details.
-
Dear Mr. Virtuali,
If you do add-ons for FSX and would like to give your feedback about what you would need to interface with GSX with your application, JOIN that area on our forum this way:
1) If you are already registered on our forum, just send me a PM (Private Message), so I can enable your user account to access that area.
As the others people talked about combining the GSX with 3rd party developer. I really hope that you'll share the setting for FS2Crew (both Voice and Button Control) to combine with GSX.
FYI, I have sent you PM. I'm waiting for you reply ASAP. Thanks.
-
Hi GSX team,
could you please give me the actual status of the open API? I'd love to write some software to implement it into my own homecockpit.
Many thanks
Daniel
-
More options in the pushback in this moment this system non functional
-
will be nice if i could see the trucks from the another person whose have the GSX
-
More options in the pushback in this moment this system non functional
Just stop saying the pushback is "non functional", because this is obviously not true. As I've already replied to you by email ( so, no need to repeat it here ), the pushback works without any problems.
There are few cases when a pushback in one direction would end up with the airplane pointing in the opposite way from the exit, and the other direction will end up with the airplane into the terminal wall.
These only happens only at the LAST parking spot on long corridor with only one exit, like some parkings at KLAX. Which is why, in these special cases, we have a custom pushback route made for our sceneries, but GSX can’t automatically handle these cases all over the world, we might add in a future update the ability for users to customize pushback routes which right now is only available for our sceneries.
-
+1, when will the API be ready?
We would like to write a remote application to use id into a cockpit.
Or you could just publish offsets accessible from simconnect (like toggle output)
Regards
Dan
-
+1, when will the API be ready?
We would like to write a remote application to use id into a cockpit.
Or you could just publish offsets accessible from simconnect (like toggle output)
Regards
Dan
Yes, a button to automate direct push back (program via FSUIPC?) would be good. This would work great for cockpit builders, using the console right now just breaks the realism.
-
Yes, a button to automate direct push back (program via FSUIPC?) would be good. This would work great for cockpit builders, using the console right now just breaks the realism.
Why do it in such a cumbersome way, when a simple keyboard macro will work just the same, as I've already replied to you the following thread ?
http://www.fsdreamteam.com/forum/index.php/topic,9576.0.html
-
Hi,
My name is Robert Cezar, developer of It's Your Plane (IYP).
I've had a number of IYP users request that we interface GSX.
I'm REALLY sorry I missed this post back in 2012. Can you please add me to the Developers' Backdoor area... that is, if it's not too late.
I thank you in advance for your consideration.
Robert
-
Since there seems to be more and more solutions popping up on FSDev that do some kind of object placement via SimConnect, maybe we could get down to it and define a way to share the objects?
From my side, it could work if you exported a function that takes an argument a title of an object that is not to be removed. Then internally maybe build a vector or something.
Or make it possible to define these objects in airport definition? Using regex maybe?
-
Hi,
Don't know if the subject is still active or not but I'll be interested to have a remote GSX client to control it from a networked PC:
- All messages can be displayed there instead of the FSX display
- Menu for actions controled with Mouse and buttons
- Live time status of operations (and force end of boarding to allow pushback)
- Why not voice output in the Client as the trucks and boarding sounds can remain in the FSX environment?
Just some ideas :).
Skip.
-
I like the voice idea, it will help the prudct, also please make the catering time different for each aircraft if it isnt already. I am new here lol!
-
Hi Umberto,I have small suggestion in future update could you do something with sound,just a correction when we simmer's operate a cargo planes like 777 or other. During Boarding there is a pax sound ,any chance to change it for proper Cargo sounds for Cargo Airplanes? add to GSX menu Cargo load beside Boarding?
Regards Slawomir.
-
Hi Umberto,I have small suggestion in future update could you do something with sound,just a correction when we simmer's operate a cargo planes like 777 or other. During Boarding there is a pax sound ,any chance to change it for proper Cargo sounds for Cargo Airplanes? add to GSX menu Cargo load beside Boarding?
This has been discussed and answered so many times already on the forum: right now, GSX doesn't know if a plane is Cargo or not. This will change with a future expansion product for GSX we are working on, that will cover cargo operations in detail.
No, this doesn't mean that you will *have* to buy that, but the work being done on it (recognizing cargo airplanes as such(, would surely allow us to allow the standard GSX to behave differently when using a cargo airplane.
-
Thanks Umberto.I waiting for that update
-
Hello, My friend and me have buy recently GSX.
We use on French VA : www.dreamairlines.weebly.com
My general suggestion are following (concerning GEX) :
- Could you add the passengers model in order to see passengers go outside the truck, walk on taxiway and go in aircraft.
- Could you make choice in boarding "cargo + passengers" or only cargo for CARGO flights.
Thanks you very much.
Skyzo
-
Hi,
I've noticed on SODE pages a mention of API for GSX. Does this mean the API was actually implemented in the end?
Thanks
-
I've noticed on SODE pages a mention of API for GSX. Does this mean the API was actually implemented in the end?
Of course, but we still haven't released it. It won't be long, though.
-
So I guess SODE is sort of pre-release testing?
Either way good news. Looking forward to it.
-
It's basically done. It's just that we made so many updates to both GSX and the underlying Couatl engine (not all related to SODE) for the upcoming KMEM release, that we are planning to released them together.
-
There are few cases when a pushback in one direction would end up with the airplane pointing in the opposite way from the exit, and the other direction will end up with the airplane into the terminal wall.
These only happens only at the LAST parking spot on long corridor with only one exit, like some parkings at KLAX. Which is why, in these special cases, we have a custom pushback route made for our sceneries, but GSX can’t automatically handle these cases all over the world, we might add in a future update the ability for users to customize pushback routes which right now is only available for our sceneries.
There is a simple way to solve this problem. (I did that for a few parking spots at LSZH in the bay for the A and B gates.)
- Download the free Airport design editor (not a FSDT product - I am sorry if this should not be allowed to write here, but it helps)
- In ADE open the AFCAD of the airport you have this problem
- search the "faulty" parking positions
- search a safe nod (Taxiline-nod that is connected somehow (it can be a little away of your parking position)
- right click the nod and go onto settings
- copy the coordinates like they are into an empty txt file (coordinate format should be like this: 4.9281938 - this here are just some numbers and do not correlate to any nod in a specific scenery)
- close ADE without saving and go back into your sim
- open the GSX-Menu and go to "Customize this parking position"
- in the lower section you find a push back direction selector
- activate the directions you need (for the "both"
- if you have a bay: write into the one which normaly would end you up facing the building (or whatever) the coordinates you have copied and click on "Apply"
- now you can use the alternative push direction (When flying online: clarify it with ATC that you make a long push to somewhere)
This way will make you initially push into the "wrong" direction initially, but then it makes an 180° turn and pushes you to the desired spot.
With my example of Zurich:
e.g. Standing at A44 alternate push will push me onto taxiway F facing North (the taxiway in front of the bay)
- my push initially pushes me into the Airside center (the building with the big "Zürich Flughafen" inscription) and then backwards onto F.
Hope this helps.
-
Small bug/issue I noticed. If you fuel your aircraft BEFORE you call the truck, the fuel truck will infinitely wait.
-
Would be great to have some DLL to import into VS.NET Projects to interact directly with GSX
-
Hi Umberto,
I thought it would be very comfortable for users of JeeHell FMGS (A320 glass cockpit software) if GSX could tell some states to an FSUIPC offset.
For instance if "GSX Ground operations" starting it would be great to read out an offset to trigger another JeeHell Offset for "EXT PWR AVAILABLE" and vice versa if the tow truck connects or ready for "direct taxi out".
I am pretty sure you don't want to support different types of Aircraft but at least this one offset could be a good starting point. :O)
Regards,
Peter
-
I thought it would be very comfortable for users of JeeHell FMGS (A320 glass cockpit software) if GSX could tell some states to an FSUIPC offset.
I'm sorry but, GSX doesn't have any relationship with FSUIPC.
For instance if "GSX Ground operations" starting it would be great to read out an offset to trigger another JeeHell Offset for "EXT PWR AVAILABLE" and vice versa if the tow truck connects or ready for "direct taxi out".
I'm sorry, but I don't understand this sentence. No idea what's JeeHell is or what you are trying to achieve. There are several L: variables used by GSX that developers can read to check the status of a service, see the last pages of the manual: is there anything that can help you there ?
-
Hey virtuali!
Who you are? Jeehell is a very big program! Have a look here! http://www.mycockpit.org/forums/forumdisplay.php?f=263
Your Programm is ONLY for ground-service jeeheel i a virtual-copy of the complex airbus-system (like AST or proSim).
So it will be good to know the software.
best regards
peter
-
Jeehell is a very big program!
Never head about it, sorry.
Your Programm is ONLY for ground-service jeeheel i a virtual-copy of the complex airbus-system (like AST or proSim).
I'm sorry but, as popular it might be amongst cockpit builders, you should really revise your perspective on the flight simulation market: a program like GSX, which can be used by everybody and works with every airplane, it's way "bigger" than something dedicated to cockpit builders with Airbus.
In any case, you still haven't clarified what exactly you would require from GSX to work with that program. Maybe, it would be best if developers of such program could contact us.
-
Dear Umberto,
I am Daniel and I am the lead developer of AST A320 software (also known as AirSimTech). I already tried to contact you. We work together with an external instructor station called FSFlightControl. The developer of FSFlightControl tried to contact you but didn't get any feedback. FSFlightControl is a perfect instructor station to be used by any cockpit builder (regardless of aircraft type) and also by "desktop pilots" who don't have a complete cockpit.
FSFlightControl would be a perfect tool to control GSX instead of having it displayed on the screen in the simconnect menues.
I will advise Andreas (he is the developer of FSFlightControl) to contact you here in the thread again.
Many thanks
Daniel
-
Hello Umberto,
Daniel pointed me to this thread - I'm the main developer behind the FS-FlightControl Instructor Station (https://www.fs-flightcontrol.com/en/).
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
-
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.
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).
-
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
-
As FS-FlightControl is an external program we can't easily access "LVars"
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.
but as far as I understood you also just use SimConnect directly (and not FSUIPC) the same as we do.
Yes.
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:
We are are obviously aware of the Simconnect client data, which is how GSX communicates with SODE...
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!
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.
-
Hello Umberto,
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.
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
-
Hi Umberto
I would really like to see a revision and extension of audio trigger points within the coding to allow the creation/integration of bespoke and regional voice and sound sets. The audio content of GSX seems to have been the same for many years and there is huge potential for improvement here. Varied and regional audio would greatly enhance the user experience/immersion factor. Making these trigger points available for the creation of freeware/payware bespoke ground audio would enhance the appeal of the product ... and the production of in-house audio sets for different scenarios takes time and resources.
Not sure this is a feature request or a request as part of the Open API. Both probably!
Kind regards
Nick
-
We are already working on that.
-
Hi,
I tried to read the LVAR with a LUA Script but did not received any values. Could someone please write an example LUA Script to read one of the GSX LVar?
My script should be started from ipcready.lua and sync the "EXT PWR" Offset of JeeHell (A320 Homecockpit Software). I am aware of setting the Offset but can't read the GSX Lvars.
L:FSDT_GSX_DEBOARDING_STATE
L:FSDT_GSX_CATERING_STATE
L:FSDT_GSX_REFUELING_STATE
L:FSDT_GSX_DEBOARDING_STATE
L:FSDT_GSX_DEPARTURE_STATE
Thanks.
Peter
-
The L: before the name it's the XML syntax used by the official gauge SDK. In LUA (assuming you use it from LINDA), there's no L: before the name, for example:
deboardingState = ipc.readLvar("FSDT_GSX_DEBOARDING_STATE")
-
Thanks. I will test and come back.
-
Thanks Umberto. Working perfectly.
Freeware Script is ready to download:
https://aviation.pero-online.de/wordpress/?page_id=1937 (https://aviation.pero-online.de/wordpress/?page_id=1937)
It would be very great if you could store the Parking/Gate Type (Gate Small, Gate Medium, e.g.) to an LVar. This would give the possibility to run certain operation depending on the Gate Type.
Great work again. I am loving GSX!
-
Hello!
Did the GSX "API" come at anytime?
Many cockpitbuilder want us it!
Please realize it!
best regards
peter
-
Hi Umberto,
how can I access the variable for PAX in GSX v2? I would like to set it for JeeHell Airbus (Homecockpit Software).
Regards,
Peter
-
how can I access the variable for PAX in GSX v2? I would like to set it for JeeHell Airbus (Homecockpit Software
All variables are documented in the last pages of the manual
-
Ups, sorry. Sure got it.
I've still used the manual from your website:
http://www.fsdreamteam.com/download/GSX_manual.pdf
Regards,
Peter
-
I've still used the manual from your website: http://www.fsdreamteam.com/download/GSX_manual.pdf
That's an outdated link, I'll fix it but, it's best you don't use it anymore.
The current manual, like every file belonging to any FSDT products, is updated by using the FSDT Live Update so, if you ran the Live Update recently, you should already have a copy of the latest version in the Addon Manager\Couatl\GSX folder.
-
Hi Umberto
Sorry to bring up an old topic again. I have a question: Is there a way to send commands to GSX Level 2 from the airplane, besides of the number of Passengers? The Idea is for example, if the airplane has the state "Engines off, beacon off, brakes set" that it would then send the command to automatically dock the jetway. So you don't have to open the commands (because P3D is only used for the graphics, not for simulation). The programm would send the commands to GSX while reading the state of the simulator. And for example, after closing the doors, the tool would give GSX the command to retract the Jetway and call the pushback truck.
It would be amazing, to send those commands directly to GSX because you could then really create remote controls for all GSX related steps.
I know it's not urgent thing, but it would be amazing if that could be made possible.
Kind Regards
Beat
UPDATE: NEVER MIND UMBERTO: found the answer in another topic: no way at the moment, but i could use macro programming on a joystick to achieve the same...
-
Hi Umberto,
One thing I would love to see would be to see two gsx passenger busses being used instead of one. I even saw two busses used for A320 plane.
Also would it be possible to update the animation the passengers boarding the plane. Usually I notice a queue being formed when boarding plane from either jetway or stairs.
It would feel more real to have a sense you are flying a lot of passengers.
Thank you
-
Hello Umberto!
Why is it not possible to open the API for GSX?
We all love your programm. It makes all flights more realistic.
But for us, the homecockpit builder it will be much more realistic to control it without a mouse and a keyboard.
So please open the API.
Best regards
peter
-
I know this is an old post but have add-ons that it would be nice if they could tie to GSX instead of them having to reinvent the wheel. If they have to do their own coding then I use them for part of what GSX does, have to go to GSX for the rest so at some point I ask what am I gaining with two apps so why not use one and drop the other. GSX does the servicing so well and if there was one area you wanted to create an API for make it the pushback.
-
if there was one area you wanted to create an API for make it the pushback
It might be more useful to us, to know what you would like to add to Pushback.
Yes, we know pull is not supported and it will eventually come, but having an API won't solve this so, if your need for a pushback API is because you feel some part of the procedure flow should be changed, we'd rather doing it ourselves, to the benefit of all users.