I am not using it midflight. I’ve just noticed it freezing midflight. It’s also desyncing in terms of the simbrief flight plan saying it does not match for some reason. I do have a full streamdeck profile for GSX but resetting GSX or disconnecting and reconnecting couatl does nothing.
Great. I’ll give that a try and see if it fixes things. Also I’ve tried to join your forums but, am still awaiting approval by Admin (It’s been 2-3 days). Any chance that could be expedited so I can discuss any issues encountered with the app on there? Cheers.
I read on their forums from other people having the same issue to make sure it was unchecked. Mine is unchecked.
The latest build crashes a lot! I had to go through 5 or 6 restarts with Fenix, to get GSX to work after arrival! It also froze all the knobs and when I restarted manually, the knobs on the plane started working again!
Tried the new version. It’s worse. It stops working from the minute I try to load aircraft. I think I am just gonna kick it out the community folder until the situation gets resolved tbh.
Version 2.9.6 works ok till now, atleast for me no problems what so ever.
3 flights with Fenix integration just worked like a charme.
No constant restarting like the version before…
Exactly, I made several flights with the Fenix, using full automation, including a complex AAOhs script
with TWO Streamdecks ( XL and Plus ) using different profiles, and checking the log created by the couatl64_boot.exe, it didn’t even tried to do restart it for the entire flight.
Yes, of course, the auto-restarter recognizes you use the “Exit” menu, so it won’t restart in that case.
1 Like
Great, thanks!
I just want to say thanks for keeping GSX updates going out regularly. I’ve been enjoying it a lot more with enhancements made in the last six months.
I hope you will consider two suggestions I have for a future update:
-
While the automatic removal during installation of jetways on 3rd party airports is useful, I would like am option to disable that scan when updating the product. Recently (I think) it has begun to automatically detect Asobo handcrafted airports and disable the GSX jetways. Many of the Asobo airports use the default jetways and I prefer to use GSX (LFPG and EHAM as examples). Currently I must remember to go into config and reactivate the Asobo airports after each update.
-
Add an option to keep the baggage loaders attached to the aircraft until boarding is completed. Currently they load the bags and then depart long before boarding is finished. In my experience (in the US) there are often last minute bags being loaded (gate checks) right up until the passengers are all onboard. The option to keep the loader attached until boarding is complete would add a little realism. Even if nothing is loaded they stay just in case.
If these are possible I would appreciate it. Thanks.
The problem is not the jetway model used, it’s how they are associated to the parking spots (the parking names) and how they are placed and how the GSX jetway replacement works.
GSX doesn’t replace jetways by replacing the Asobo model: that would result in getting the same model everywhere. It does it through replacement .BGL files, which are a 1:1 match with the parking positions of the default scenery, so they match both their names and the jetway position/rotation they had in the default scenery.
We just replace the name of the model used, so we can (at compile time, when building those pre-made .BGLs) apply GSX own operator rules for jetways.
When jetways are inserted in a .BGL, they are associated with a specific parking name and position, so if you keep a different scenery as base, like Asobo handcrafted EHAM, but replace its jetways with a .BGL made for the default EHAM, there will be all sort of issues, like:
-
Double parking spots on the Map, which results in duplicated parking spots causing both jetways malfunctions and likely AI issues.
-
Jetways not placed correctly, because the position of the replaced jetway (based on the default scenery) might not match the buildings of the handcrafted version.
The only way GSX replacement jetways could work on a non-default scenery, would be if the handcrafted/add-on scenery had all parking spots completely matching the bare default scenery, they must have exactly the same name and the jetway would have to be placed in the same position. This is almost never the case: it might have been when MSFS first came out, but with lots of handcrafted airports made independently by 3rd party developers for Microsoft, they tend to be made more and more like 3rd party sceneries, because they basically are.
For this reason, the FSDT Installer is correct in considering the Microsoft/Asobo airports like 3rd party airports, which will solve most of the problems with double parking spots and/or jetways not working.
Note that, having duplicated data about parking spots, is not just a cosmetic issue on the map, it will also affect GSX, or any other add-on that would query the Navdata API for any reason, since the Navdata API will transmit everything: including the duplicated parking spots.
1 Like
Thanks for the detailed explanation. It’s interesting that I haven’t had any issues when I activate the GSX jetways on the Asobo airports like LFPG. No duplicates, no issues with the sim, navdata, or GSX. It works perfectly fine for me and looks great.
Maybe I’ve just been lucky and only had this experience on airports that are “close enough”. I can’t say that I’ve looked closely at all of them. I’ve certainly seen the duplicate issue on airports I’ve purchased and I have those disabled (they typically have custom jetways anyway) but these original Asobo airports have been fine.
I’d still like to not need to adjust my config after each update. I get why it would be done on first install but if I’m happy with the results of my config setup it would be nice to keep it unchanged.
Hello, I have the same problem, did you find the solution?
Your probably haven’t checked all, or maybe you already have 3rd party airports for some of them, which would require having jetways disabled in any case.
I do recall some handcrafted airports that surely don’t work with GSX replacement jetways, are EDDF and EGLL: you can clearly see the jetways are misplaced and, on top of that, they don’t even work.
That’s how the GSX Config page worked when GSX first came out: it EXCLUDED airports from Microsoft and Asobo from being automatically Disabled, with a note on the manual explaining “use your judgement”, because they really were a case-by-case basis, some worked, others didn’t.
However, in time, the following happened:
-
Nobody read the note on the manual about taking care to check Asobo/Microsoft handcrafted airports.
-
More default handcrafted airports were sub-contracted to 3rd parties, possibly using different databases than default, possibly further improving (thus changing) on the default Navdata
-
More and more alternatives for those airports became available on the Market (ex. EGLL, KLAX, etc.)
-
The number of users complaining about jetways or passenger bugs on those airports kept rising.
So, at a certain point, we decided to treat Asobo/Microsoft handcrafted airports like any other 3rd party airport, so they’ll get disabled automatically.
But I see your point: some of them might still work so, maybe, we can make an OPTION “Exclude Asobo/MS airports from being Disabled”, which will default to off, but can be optionally turned on.
Ideally, it should be done after installing a 3rd party airport. But the problem is, you can’t enforce something like that, and users forget to do that. I even forget it myself…
So, the next best thing, is doing it as often as possible, at least to minimize the risk of somebody installing a new airport and getting conflicting jetways, so on every GSX update, which are very frequent, reducing at least the time a user would stay in the conflicting situation.
Most, I’d said almost ALL issues most people point as “GSX bug”, are just a result of having forgot to run the automatic exclusion after installing a new scenery OR not having added the airport manually, if the scenery doesn’t respect the official SDK naming convention (usually freeware)
This, in fact, is one of the most frequently asked questions, which causes us lots of support effort, which is time taken away from actual improvements.
A “foolproof” solution would have been something extremely invasive and likely very unreliable or prone to issue, like a “monitoring” program that starts with Windows, and will monitor changes in the Community folder so, each time you add a new scenery by any means, it should quickly disable the GSX replacement file for that airport, so you won’t have to “remember” to do that, or even know you have to do that. But it’s a very messy solution, and we don’t really need yet another program that starts with Windows…
1 Like
Some posts removed.
A reminder that the MSFS Forums are not support for 3rd Party. Take all support related issues directly to the 3rd Party Developer.
From the Code of Conduct:
Advertising and 3rd Party Addons
This forum is not to be used for any non-MSFS related businesses, organizations, or websites,.
… 3rd Party Support/Bug Reporting should be sent to the designated support funnels of each 3rd Party Developer, and should not be conducted in these forums.
Further warnings will result in the following:
- Receive a formal warning; or,
- Be banned from the forums for a length of time based on the severity of the infraction up to, and including, indefinitely
Hello - no I just kept amending the fuel figures each time! Haven’t been flying the BCF recently, so not sure if anything has changed.
Thank you for your reply
Sadly there is still no GSX integration for BBJ and Cargo variants.
I have lost all sound from GSX - from the cabin crew saying “welcome onboard” to the pushback people - everything. I have updated the program, and nothing is changed in my sound settings. So frustrating!
I haven’t touched anything here and it appears to be exactly the same as I left it 2 days ago when it was working just fine.
Is there a way to get rid of the jetbridge sounds? Every flight i load with real traffic it’s a constant beep from those jetways 
Furthermore, if i didnt said it yet , gsx is on of the best addons at the moment to get the real feeling in the sim
1 Like