Because people don’t have time to read articles after articles to get an issue that wasn’t there fixed. I know it’s frustrating for you too but that’s the reality. Seems like the latest update resolves the issue when the disable hotfix box is checked!
I don’t get these complaints about frequent updates. And then there are complaints when there’s no update for a couple of weeks. I like this hotfix system - it works fine for me, I don’t need to exit my flight sim for it and I’m always sure I have the latest version and fixes.
8 Likes
Does anyone know why GSX needs to be activated in the toolbar menu again after landing?
I used it for departure (boarding & pushback) and as you can see GSX is active before take off.
About an hour later I want to select the gate, but GSX menu won’t open when using a keyboard shortcut. Quick look on the toolbar and GSX is deactivated. I have to click on it and only then GSX menu shows up.
It’s done on purpose: after you take off, the GSX entry is Deactivated, so it won’t do anything in flight, zeroing even the minimal impact on performances of the menu code itself, and minimizing the risk that, opening the menu accidentally in flight might possibly cause an issue with Simconnect possibly crashing or freezing in case bad Navdata in the area you are flying it.
4 Likes
So, integration with BATC is pointless now if I have to remember to manually activate GSX after landing and before ATC assigns me a gate.
2 Likes
That’s not true. GSX can be remotely controlled by an external app with the menu completely closed, like the Fenix, the iniBuilds A350/A340, the Leonardo Maddog or the FsLabs A321 all do.
The active menu is only required if you want to open the menu with the hotkey and to issue text messages (screen tooltips), not to take commands from external apps.
In fact, the menu it’s just like an external app, because GSX by itself, it’s always remotely controlled by something else, the menu, the airplane, a completely separate application, it makes no difference and it doesn’t even know who’s controlling it.
3 Likes
Maybe in theory, in practise the integration with BATC stopped working. It used to work more or less fine, if couatl process didn’t crash and restart mid-flight. After a quick search on BATC discord it appears I am not the only one with this issue.
Not in theory, but in practice too. Otherwise you’ll have to explain how Fenix (and many others apps), can possibly work with the menu entirely closed, and they surely do.
What the BATC integration was supposed to do, when the menu was open ?
Could be they are sending the hotkey instead of setting an LVar to open the menu, which is what Remote Control is documented to be used ? That’s the only possible reason I can think of that it would work with the menu active, but not when it’s not active. What if you decided to keep it inactive then ? Clearly any remote control should (and it is) independent from the menu status.
I’ve not done any airline flying for a while but yesterday fancied a change. Updated to latest GSX version, BATC latest experimental version and Fenix A320 all upto date.
As you mentioned I too Noticed that the GSX interaction didn’t seem to work like it used to. It used to work and interact flawlessly.
Also I had checked the option to disable hotfix but was still getting the prompt in the gsx menu.
3 Likes
Is there an issue with fenix and gsx?
During pushbacks it stutters horribly. Updated gsx, no improvements
1 Like
Something is really not right, since multiple users confirmed that hotfix notifications won’t appear anymore if disabled, the only possible reason is you got a partial update due to cloudflare delays, so update using the Offline isntaller.
I don’t have to explain anything. It was not me who made changes to how GSX works in the background. The fact is integration with BATC stopped working after recent updates to GSX. Obviously, it’s your software and you can do whatever you want with it. I don’t have anything more to add. EOT.
1 Like
that “obviously” sound very absolute without any evidence, you assumed we “changed” GSX works with BATC, but GSX doesn’t know anything about BATC, it’s BATC that controls GSX, and GSX has no idea who’s controlling it.
I’ll surely ask BATC what the problem might be and how they control GSX (BATC is also updated very often).
One thing I have noticed in recent flying of the Fenix aircraft is that I used to be able to go right into the Fenix EFB after installing the Simbrief flight plan and tell it to load fuel using GSX and I’d instantly hear the message about the fuel truck coming. GSX just started automatically when the Fenix loaded. Now, if you don’t actually click into GSX with the toolbar first, the fuel request doesn’t work. Problem with that is that once you then do start GSX, the button to load fuel is grayed out and no longer available. Perhaps some option changed that I didn’t notice in either GSX or Fenix but I can’t find anything to update.
1 Like
How do you explain this isnt a GSX issue
https://gyazo.com/b864c31b136590db557945efc1f02ed2
And once again no passengers deboarding only cargo
restarted GSX and wow Airport has magically grown a Jetway that was there all along
1 Like
Of course it’s not a GSX issue.
When you arrived, for some reason Simconnect didn’t send the list of parking with jetways which GSX asks when you land so, as far as GSX was concerned, there was no jetway there. The most common case for this is after a flight, Simconnect might become stuck and stop sending data, or sent incomplete data, or if was just too busy loading the airport during the final approach.
Then you restarted GSX, so with the new connection, a new request was made again, and this time Simconnect replied and/or the simulator wasn’t so busy as it was during final approach so it could reply with the complete data about the airport, so now GSX sees a jetway.
Just today, an user on Discord suggested this could possibly be caused by the “MaxClients” settings in Simconnect.XML that normally defaults to 64, but with several addons running it might not be enough, and many users change this to 256.
We just updated the installer today, so it will automatically set the MaxClients value to 256 automatically when run, so these weird Simconnect-related issues might go away.
5 Likes
The thing that I noticed with regard to BATC with GSX integration is that it used to be that when BATC would assign a gate for you, BATC would then send the gate assignment info to GSX, where it would then be tasked with setting up that gate for arrival no problem. After the change where GSX now eliminates the gates that it determines are too small for your current aircraft, if BATC selects one of those gates, nothing will happen until GSX is told to allow that gate to be selected, so you need to open GSX up, select the terminal, then allow the unshown gates to be visible, and then select the gate manually. I wonder if that is what you might be experiencing?
I do understand that you can change the size of the wingspan allowed at a specific gate to accommodate your aircraft via the editor, but most times, when you are at the end of a flight and you don’t know which gate BATC will assign to you, the last thing that you want to do is stop everything and either go through the aforementioned procedure for gate selection and/or editing the gate config.
It would be nice perhaps to allow a GSX setup feature that would allow disabling the size restrictions at gates. Just a small thought on my part.
Also, I think GSX is a great add on that really adds so much to the overall flight sim experience.
1 Like
Maybe this is the problem, because the by-wingspan gate filtering works in the same way as the by-airline gate filtering which has been there for far longer: the menu has an option to turn off the filters, which would be obvious to you as an user when using the menu, but it might not be recognized by BATC when it remote controls GSX.
Fact is, did it work with the airline filter ?
Maybe the airline filter doesn’t appear that often as the wingspan filter ( there are way more airports with too small wingspans that airports with airline codes at the gates ), so nobody noticed that before, but the same could have happened with the airline filter too, which is there since FSX/P3D times, since everybody back then coded airports with airline codes, because ADE allowed to edit them, but in MSFS the default editor doesn’t have a way to edit them (even if they work when manually adding them in the source code, since they are supported in the .bgl), so we always had a filter based on airline-preferred gates.
Maybe we can set up LVars so that 3rd party apps can momentarily disable both filters when they are in control, since when a human is in control, the filter on/off option is right there as the first menu item, so it’s easy to use.
2 Likes
With GSX installed, is it recommended to turn OFF the “Airport Services Quantity” setting?
Similarly, is it also recommended to turn OFF the new option that allows enabling or disabling ground services at airports?
It is really horrible!! The integration GSX and Inibuilds a350 is really bad!! Why does it have to be so difficult and different with every SINGLE aircraft, couldn’t they harmonize the process so we have a similar groundhandling process with all aircraft? GSX works horribly and Inibuilds does not work well either!! We custormers don’t deserve such horrible products and negligent companies producing them!!
1 Like