ok, thank you for clarifying the reason.
Is GSX down today? Doesnāt seem like it wants to start! Trying to āCheckā for update is also a very slow process ā¦
This issue sounds like what a few of us are experiencing, though weāve been told itās not an issue with GSX 
Very disappointing! It was working somewhat ok yesterday but not today! It doesnāt want to work! I have reinstalled it, and everything, tried to restart it several times and have spent the last 50 minutes trying to start it! Doesnāt want to start! It is useless at this point.
In general, I do appreciate what Umberto does, but this many updates in a short period with so many issues, is just not very good! This thing was working fine before Version 4.00. No issues or very little issues and now there are so many issues! I personally donāt have the time to go to various forum to report issue after issue! I just want a product that works somewhat properly! GSX is not working properly now and thatās disappointing.
There are no issues with GSX begin ādownā and, in fact, your report of āCheck for updatesā being slow confirms it.
Remember, thereās no such thing as a āGSX serverā that can be eventually ādownā, nobody ever connects to an FSDT server, everybody (including me!) connects to it through their local CDN nodes.
So, if the Installer ( which is not GSX) is slow checking Updates, it must be a problem with your local Cloudflare node because, even if the important code files are now hosted on GitHub, Cloudflare is still used for the less important files, those where a problem would at most cause losing an recently operator texture (pink textures), but not serious problems.
And, of course, while being a different CDN, GitHub is still a CDN, so we canāt say for sure it will ānever downā or it will ānever slowā, or that your local GitHub node will āneverā have issues, thatās the nature of the thing.
So, before saying GSX has a problem or GSX is down, always be sure you have the latest update, and the only way to be sure of it, itās to download and install the Offline Installer which now has a dedicated button in the Installer, so itās easy to find.
Many thanks for your reply.
I know it is not just me having this issues as Iāve heard so people friends and other people also having this.
Iāll do another flight and send the logs in discord.
But please before doing that, ensure you tried the Offline Installer first, I need to be sure you have the latest version, including hotfixes (we had a couple since 4.0.3)
Will do that!
Do I just need to click the offline installer button on the fsdt inatller app and follow the steps?
Yes, the button downloads the latest offline installer, and runs it automatically.
Many thanks.
Will give it a try later.
You also said with absolute certainty that the text above the marshaller 100% definitely disappears after youāre parked every time only to release a patch to fix that a few days later - for which Iām grateful, but I would appreciate you leaving some room for the existence of errors. You cannot tell me that you have tested GSX with every possible combination of GSX settings to guarantee that the issue myself and other users are having with its inability to open or stay open is ānot GSXās fault.ā No oneās QA is that good.
Nowhere I ever said GSX has āno bugsā and, what the things labeled as Fix in the Changelog, other than publicly acknowledging a bug ?
Your issue with the marshaller text was a very minor issue that wonāt even happen in every case (it depended when you called the next service, usually deboarding ), and that was something that required specific testing, the problem reported before seemed to indicate a completely unusable GSX with the Fenix, a very different situation, and itās something that, as Iāve said, I always test before an update, for the following reasons:
- It interacts with GSX in ways that we might not have anticipated, because it controls it
- Itās a plane I know and trust.
Not talking about the Fenix, Iāve experienced this in every flight for the last week or so. I just did the āOffline Installerā and now itās showing that I have 4.0.4 installed but 4.0.3 is the latest, which it says to use the Offline Installer to resolve.
Also in the flight I just completed the marshaller text still does not disappear.
Nor did I claim you did - my point is that when I initially reported the issue, you very confidently told me my problem was impossible and that it definitely worked correctly every time. Is it within the realm of possibility that you are wrong on this issue as you were that one?
The offline installer reporting 4.0.4 is just a side-effect of its build process: you just got the manifest for the next update, but itās just a visual issue that has zero effect on anything. You DO have the latest 4.0.3 update.
And yes, of course Iāll check again the marshaller text issue, because nobody ever reported it to be still happening, you are doing it now.
Again, my bigger issue now is that GSX will not open or if it does it will not reliably remain open long enough to perform meaningful ground services - as is being reported by multiple users above, and not just with Fenix automation. You have claimed this cannot be, just like you claimed the marshaller text issue could not be, so I am asking you to please leave an inch of room for the possibility that you are wrong.
What else can I say, other than confirming I cannot replicate any of the issues reported ?
You are trying to steer this into āyou were wrong beforeā using the very minor marshaller text issue to prove your point, but thatās not how things are checked properly.
The proper way of checking things, is with reports and do the proper troubleshooting to understand why what is happening to YOU is not happening to ME.
Because, why I think the marshaller text issue should have been fixed, I was still unable to reproduce it, not before not now, so it was another fix āin the blindā.
And please, donāt try to start troubleshooting here. I have been warned by moderators several times this is not the place so, if you want your problem to be properly checked, do the troubleshooting in the proper places, so we can check logs, other add-ons used, everything.
As I said, you can approach issues reported by users with a sense that your software is not perfect, and admit that simply because you are unable to recreate them does not mean the issue does not exist within your software (and not simply a user error). I have no interest in troubleshooting here, and my interest in this product fades with each reply of yours. Iāll check in after the next update to see if GSX will start for me, and until then Iāll just keep this thread muted.
You keep giving my āI cannot replicate itā sentence additional meanings that donāt exist. That sentence means literally that, the parts were you think Iām claiming the issue cannot exist and even more itās the āuserās faultā are completely and are never my intention.
By saying āI cannot replicate itā:
-
Iām NOT saying āitās the user faultā - this is completely made up.
-
Iām providing TWO very useful informations:
- Itās not something that is supposed to happen normally.
- Itās a request for the user help to provide additional informations.
Thatās what āI cannot replicate itā means. Nothing else, and itās already an useful information for users to know how to start some real troubleshooting.