I would love to see that in action!
Is anyone experiencing long delays with boarding/deboarding? Sometimes passengers start boarding 5-10min after I select a command from the menu. Yesterday I selected deboarding after I landed, stairs connected, doors open, baggage is being unloaded but passengers stayed on a plane for 10 minutes until they started getting off.
@Umberto67 This is a great idea! The ability to keep th âshow me this sportâ open until you get within say 50 meters of the parking position. Good idea @DaveR44
Hmm everyone is loading the wrong containers into the Fenix in all YouTube videosâŠ
These are the correct containers loaded into an A320:
A full container is not able to move past this strut after loading, only the LD3 container type can:
How many LD3 container designs has GSX?
Is it possible to make customized container textures with own brand designs?
You are wrong. The containers that are charged in an A320 are LD3-45W (AKH), and are the ones GSX uses by default to load our virtual Fenix A320. See this: A320neo | Airbus, or this: A320ceo | Airbus, and this: https://vrr.aero/products/akh-container/
In the video you showed, they are charging an A321, wich can use a different type of containers than A319 and A320, LD3-46W
The default configuration for GSX for all A320s (Asobo, Fenix, FBW), has always been the AKH container, which is made specifically for the A320
Of course, users are free to change it with any other type, or to use Belt loaders instead. And itâs even possible to create airframe-specific configurations, so one airline might use ULDs, another one Loaders.
Is that something you can do by airline code? For example, BA use containers exclusively.
Thx
These are the last changelogs for the past days, following the release of the new KIAH airport, which required some updates to GSX as well.
Version 2.6.1 â May 26th, 2023
-
GSX Pro NEW: A new option in the GSX Settings â Timings section, allows to configure the amount of time the pointer used by the âShow me this spotâ feature will stay on screen. The slider can go from 5 to 30 seconds (15 by default), with the last notch used to keep the pointer on screen, only to disappear when you are within 100 meters from the destination spot.
-
GSX (all versions) NEW: Erasmus Catrering (Netherlands) added at EHRD. Viggo handler added to EHAM.
Version 2.6.0 â May 23rd, 2023
- GSX Pro NEW: New L: variables available for developers, to know the exact name, number and suffix of the Parking position selected in GSX:
L:FSDT_GSX_SetGate_Name
L:FSDT_GSX_SetGate_Number
L:FSDT_GSX_SetGate_Suffix
Check the âDevelopersâ chapter in the manual, which has been updated to explain how it works, complete with an example to create a door behavior that interacts with GSX, to be added to airports.
-
GSX Pro NEW: To save on the number of Simobjects created, airport profiles can optionally choose not to spawn a static VGDS when the airport loads, and use only the dynamic version, when a gate is selected in GSX. The option is by profile and is set in the âDetailsâ page, in the Scenery Customization.
-
GSX Pro NEW: Support for KIAH stairs-like Jetways on Gate B.
-
GSX Pro NEW: Added new customization parameters in the airport profile for jetways with moving custom roots and extra waypoints.
-
GSX (all versions) Change: Many tooltips in the Settings and the Scenery customization page have been added, and many have been reworded to make it clearer what each option does.
-
GSX (all versions) Fix: The Trashcan icon in Pushback slots is now enabled only if any of the data fields in the slot have been edited. Also, when clicking the Trashcan, the âSnapâ option will be disabled, which is the correct default value.
-
GSX Pro NEW: Internal airports database now correctly supports Parking Suffixes (required by KIAH).
-
GSX (all versions) Fix: Error when testing a Jetway twice and quickly in the editor.
-
GSX Pro Fix: Bad data about jetway heading wonât be saved in the airport profile anymore. The issue was harmless, since in MSFS the jetway_pos is not used, but it was fixed anyway.
-
GSX (all versions) NEW: Added the following Handling operators: Air Vanuatu, Vanuatu Terminal Services (Vanuatu), Accufleet( USA ), NĂŒrnberg Airport Handling (Germany), Flight Support (Turks and Caicos), Philippine Airport Ground Support Solutions (Philippines), Venezia Airport (Italy), Linz Airport (Austria)
Version 2.6.2 â Jine 8th, 2023
-
GSX Pro NEW: If both the airplane and the parking position have matching airline codes, the GSX menu by default will hide positions not suitable for your airline when showing the list of parking spots in a group (all groups will always be displayed), with the first menu option used to remove the filter to show all parking spots. This requires airline codes in the parking to be included in the GSX airport profile, since they canât be read from the scenery directly when using the Navdata API.
-
GSX Pro NEW: GSX now recognizes airplane variations in separate packages, allowing to read airline parking codes from the aircraft.cfg in the Variation folder.
-
GSX Pro NEW: If the airplane hasnât set the airline code in its aircraft.cfg, GSX will read the airline from the currently active SimBrief flightplan.
-
GSX (all versions) NEW: When editing a parking spot, using the âTestâ function (NumPad 5) will show the Parking Distance Threshold as a green circle. Pressing the key again will turn it off. The Test Jetway function continues to be available when editing the Stop position instead.
-
GSX (all versions) NEW: Added the following Handling operators: AST Aeroservizi (Italy), Envoy, PrimeFlight, Silver Airways, Quantem, Triangle Services (USA), Stobart Aviation (UK), Tradewinds (Kenya), NAHCO Aviance (Nigeria), Nauru Airlines (Nauru). El Al (Israel) logo updated.
-
GSX Pro Fix: Donât remove airplaneâs own Traffic Cones when the parking is activated, if they are created as separate SimObjects (ex: Fenix A320), unless the airplane profile is set to use the GSX Traffic Cones instead.
-
GSX Pro Fix: GSX Trial now working correctly at FSDT airports if the airports are activated but GSX isnât.
-
GSX Pro Change: Updated default GSX Profile for FSDT KIAH.
So, I went to update to 2.6.2 but I get an âunhandled exceptionâ error. If I click continue or click quit nothing happens.
Googled the error and couldnât find a solution. Went to your forum and had to register and 14 hrs later Iâm still awaiting a confirmation email so I can get on your forum to get this solved.
Becoming impatient I thought, Iâll just uninstall and reinstall. So on the updater I hit the button for you to email my activation key, in case I would need it. Well, 12 hrs later and Iâm still waiting for you to email me that as well.
So, pushing on 15 hrs now, I canât get a key off of you and I canât get a confirmation to get on your forum to get this solved.
Therefore, could you please extend me the courtesy of offering me a solution to your broken product here as itâs becoming wearisome trying to solve this through your own support services.
Attached is screenshot of the error.
In order to get support, you should use either the FSDT support forum or the FSDT support email, which is always available while you wait for your forum activation
I checked the forum, and there are only 3 registrations pending to be processed, all in the last hour.
Yours was already been approved way before and in fact, I checked again and, the activation and the related email alert for somebody with a forum name similar to yours ( so I assume itâs you ) has in fact already been sent.
Also, nobody using the email you used on the forum, has ever sent anything on the other support channel, the support email, the one you are supposed to use and which is always available, no matter your forum registration status.
Be sure you will be supported, if you use the proper channels, and this is not.
Current version conflicts with the pilatus pc6 xbox livery. Delete it in your content manager and coatl should start up just fine.
From the GSX manual:
âWe have found that the most efficient way to provide customer assistance is through
the forum, because a solution to an issue posted in public could benefit many users
at time. For this reason, all questions should be posted on the forum. Please
DO NOT send messages via email requesting question about use of the product or
submit bugs. You should email support only in case you need a reactivation.â
Now you know 
Thanks for the suggestion, but thatâs not the problem here as I cleared out all the default X-Box, Aviatorsâ Club, Kenmore etc etc liveries years ago.
Thatâs why I said:
In order to get support, you should use either the FSDT support forum or the FSDT support email, which is always available while you wait for your forum activation, which in the OP case, was already processed when he posted here.
No, it doesnât anymore, it was a problem that lasted for a few hours, and of course has been fixed as soon it was reported.
Sounds good. Will be updating thanks!
Is anyone getting the following error at any airports -
I am getting this error at the default (standard edition) KORD at any gate and in any aircraft. Doesnât seem to happen anywhere else - just at KORD (from my limited testing at about five other airports).
I did some initial googling and just found some issues in the past with the P3D version. Iâm not sure if it was a result of the recent update or not. To be honest, I donât usually use KORD as a departure airport, so Iâm not sure if this is due to the recent update. Iâm on the latest (2.6.2) GSX Pro. All world updates are up-to-date.
Any help on this one would be greatly appreciated!
Thanks!
@Umberto67
Hello
I think there is a problem with the latest version â2.6.2â It is no longer possible to save aircraft customizations with the 3D editorâŠ
If I click on one of the options and I save to save my configuration, the next time I open my options are unchecked, return to âstandardâ mode
Same for the configuration of the plane, for example, if I change the point of contact or the tank truck must attach the pipes under the wings, it doesnât save either⊠
Same happening with meâŠ
I posted it in the GSX Forum, I understand the developer is aware of our issue