What I was trying to imply was how there might be some issues with your GSX Pro that needs to be addressed. I often get the impression when people are reporting issues in here, how they mostly will hear how they did something wrong, didn't read the documentation or how what they say/report simply can't happen.
The problem is...most of the time this is exactly what is happening, if you follow the threads up to their completions because, of course, when something IS really "a bug", IT IS fixed.
A great first step to fix bugs, is always trying to make a report as precise as possible, so we can REPLICATE IT.
Like they were imagining what they are reporting. The issue discussed in this thread is such an example. Where both others as well as I have seen how the fuel truck leaves pretty much instantly. Even after following all your advice.
See this post here, same issue, the user was convinced he "followed all advice", except he had enabled the "Detect custom aircraft system refueling" option which is disabled by default, without fully understanding what it does. While agree the manual COULD have been more clear, it was no GSX bug.
https://www.fsdreamteam.com/forum/index.php/topic,27449.msg179650.html#msg179650Based on the number of threads in here as well as clips on YouTube showing all sorts of weird things happening, maybe some additional time should have been spent testing the software before it was released. Obviously, I can only speak for myself but I think it's safe to assume, most of us when buying a software just want to enjoy the software. Rather than constantly troubleshooting or being worried of doing something in the incorrect order or whatever.
The number of threads here is only an indication of the program popularity, which we weren't even prepared to, which is related to the bigger popularity of MSFS itself. However, citing YouTube videos as an "example", when MOST of the issues I see in many popular streams are:
- Passengers boarding incorrectly because the jetway didn't dock, which didn't dock because the YouTuber had a 3rd party airport with GSX Jetways, because they weren't disabled as they should.
- Passengers walking in the air, because the jetway docked on another door, in one case it docked on the service door, with the head twisted. Saw this in a YouTube video, with the presenter and users all commenting "passengers walking in the air", without even noticing that, in all that scene, the only thing right were...the passengers, which were walking on the correct path, it was just the jetway that docked on the *right* side of the airplane!
- Refueling not working because I keep seeing that "Detect custom aircraft system refueling", enabled (when it's Disabled by default), because it seems many assume that option would result in GSX recognizing any kind of custom refueling system, when in fact it's used in a very limited case, with a plane with a turnaround time that refuels after a delay.
- A YouTuber said GSX fuel counter indicate was "wrong", because he didn't realized the counter always count Gallons.
- Issues in general due to the use of Marketplace airports, which can't be read by GSX. Nobody can reads those.
- Problems with users not getting pop-ups or notifications, because they closed the toolbar icon when they shouldn't have, which stops the menu and the tooltips to appear until the toolbar icon is reactivated again.
When you release a software, IMO part of the goal should be to develop a software that is robust enough to handle user error and mistakes. Without the complete thing ends up in a big mess. When you have a software such as GSX Pro with all these issues, be they user-related or bugs within the software or a mix of both, many users quickly will lose interest in using the software.
You might have a point, if we really "designed a software", that is we made the WHOLE software. Unfortunately, GSX MUST work within the MSFS SDK limitations, which in some cases are very "limiting", we already explained them so many times:
- We don't know where jetways ends up when they activated. We don't know WHICH door they have been docked to, and we need to rely on a dirty hack to even know if they *docked* somewhere, by checking their hood animation, because there's no way from the SDK to know which door (if any) the jetway has docked to.
- The code that runs the menu, which is Html/JS, gets killed immediately as soon the user click the toolbar icon to disable the menu, and doesn't come back again until the *user* will reactivate it again. This means, during a procedure that would normally require GSX displaying another menu after some time, like during Refueling or Deicing, when extra menu options are supposed to be shown *after* the vehicle arrived, if the user closed the toolbar icon, there is no way for us to show that menu, unless the user reopens it again. That's because it's not possible to reactivate a menu from Simconnect, only from JS, but our JS code has stopped the moment the menu was closed.
- The jetway animation systems has bugs, it lose sync between LOD, so user "think" the jetway disconnected, when in fact is only showing its deactivated LOD, because the animation lost sync with the switching LODs, this obviously happens with default jetways on default airport and has been reported to Asobo more than a year ago, yet users are noticing it only now, because when passengers pass through jetways, it's more noticeable, and it's assumed its a "GSX bug", when in fact passengers are working perfectly fine, the jetway hasn't, just like the default jetway in default airport.
