Products Support > GSX Support MSFS

GSX Pro Short-term Roadmap: what to expect in the next updates.

<< < (4/37) > >>

arpal:
Hello
Any plans to correct the marshaller's message "left is clear, right is clear" while still being at the nose wheel removing the gear pin?
and also his/her incorrect position to show the pin to the crew (being on the opposite side of the pushback route so then having to walk in front of the aircraft)?

kev649:
Hi Umberto

I have a problem with Jetways not quite reaching the aircraft and stopping short so consequently passengers walk in mid air for a short period till they reach the aircraft. This even happend on my payware airports, and before you ask, yes i've excluided the payware airport jetways in the configurator.
Is this due to be fixed with an update or is there anything i can do to fix it. We could actually do with a jetway editor in gsx pro like that which is in gsx level 2 for p3d.

Thanks

virtuali:

--- Quote from: kev649 on October 06, 2022, 09:50:02 pm ---I have a problem with Jetways not quite reaching the aircraft and stopping short so consequently passengers walk in mid air for a short period till they reach the aircraft. This even happend on my payware airports, and before you ask, yes i've excluided the payware airport jetways in the configurator.
--- End quote ---

Since it happens with 3rd party jetways too ( it happens with default airports with default jetways ), it indicates GSX cannot possibly have anything to do with GSX, and it's a know limitation of the default Jetways animations system, which can happen even with default jetways on default airport. Fact you call a jetway from the GSX menu doesn't change how the jetway would work, since the only thing GSX does to call a jetway, is just sending the standard Jetway Trigger command, without any involvement how the jetway works ( or not ).

While it's entirely normal that a jetway might not work on a certain combination of airplane, jetway model and placement and parking position, the real problem is there's no way for GSX to KNOW where a jetway docked, or if it has docked partially, nothing in the SDK allows that, so GSX can only assume it has docked correctly, and will generate passengers based on that assumption so, in a way, when you see passengers "walking in the air", passengers are the only thing working in that scene, because the real issue is the jetway docked incorrectly, with no way for GSX to know that.

The only thing you can do, from GSX, is customize the STOP position, to ensure the airplane will end up in a place where the jetway would work and, since the Stop position is relative to the airplane Preferred Exit ( different planes will stop with their own Preferred Exit in the same position ), you can "reasonably" sure if it works for an airplane, it should work with many others. That's why there's a Jetway TEST function in the Parking editor ( NumPad5 while editing the Parking Position ).




rsm2000e:

--- Quote from: virtuali on September 28, 2022, 04:22:00 pm ---
--- Quote from: rsm2000e on September 28, 2022, 03:42:26 pm ---Please consider my request to add a "disable all stairs"  GLOBAL option for entire world airports - why?  For those simmers who fly tubeliner jets and park only at airports with jetways! 
--- End quote ---

In most of the world, except for the US, the rear staircase is used for the cabin cleaning crew. Passengers won't use it if there's a jetway.

--- End quote ---

Since I fly ONLY in the USA, it would be very helpful if you would consider adding a tickbox to the GSX setup to "disable rear stairs" entirely, please and thank you very much.  In USA, I have never seen them use a rear stairs at an airport that had jetways (as you correctly state).  So therefore we who fly only in USA are left with having to disable rear stairs by editing each and every airport we fly to... which is not convenient and a huge consumer of time, whereas from a programming standpoint seems quite simple to do?  Thank you Umberto.

Lorenzo.D:
please add an option for the quick edit  pushback  function to activate push only when i need not when i push enter to confirm the pushback route. thanks

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version